Skip to main content

How to troubleshoot REST API actions

Updated over 3 weeks ago

Summary

This article helps you troubleshoot common issues when using REST API actions in Astra. It covers frequent problems such as missing form parameters, limitations with lead data, authentication errors, and important security considerations to keep your integrations working reliably.

Instructions

Form submitted: parameters not being passed

Problem

Your REST API receives empty or missing values when a Custom Form is submitted.

Why this happens

This usually occurs when the placeholder used in the REST API configuration does not exactly match the form field name.

Matching is case-sensitive and based on the placeholder suffix (the part after the last .).

How to fix it

Make sure the placeholder suffix exactly matches your form field name.

Examples:

  • Form field first_name → Placeholder {{first_name}} or {{contact.first_name}}

  • Form field firstName → Placeholder {{contact.first_name}}

    • Reason: case mismatch (firstNamefirst_name)

After correcting the placeholder, save the action and test it again.

Lead captured: custom fields not working

Problem

You want to send additional or custom fields with the Lead captured event.

Why this happens

The Lead captured event always sends a fixed request body structure. Custom fields are not supported for this event type.

Any custom request_body configuration is ignored.

What you can do instead

If you need to send custom data, use one of the following options:

  • Form is submitted event with a Custom Form

  • Intent-based trigger with a customizable request body

These options allow you to control exactly what data is sent to your API.

Authentication errors

Problem

Your API returns a 401 Unauthorized error.

How to fix it

  1. Verify that your API key or token is correct

  2. Make sure the token has not expired

After updating the credentials, test the action again.

Security notes

Astra includes built-in safeguards to protect your data and integrations.

  1. Credentials are protected

    • API keys and passwords are masked (*****) when viewing action details

  2. Server-side request forgery (SSRF) protection

    • Requests to internal or private network addresses are automatically blocked

  3. Test mode available

    • Use test mode to validate your REST API action without affecting live data or analytics

Following these guidelines will help you troubleshoot issues quickly and keep your REST API actions secure and reliable.

Did this answer your question?