---
title: "API"
url: "https://help.magicblocks.ai/en/article/live-api"
language: "en"
last_updated: "2026-03-18T08:24:50.210Z"
---

# API

Before you go live, you may want to connect [MagicBlocks](https://magicblocks.ai/hc) to your CRM, analytics tool, booking system, or automation platform (like Zapier, Make, or your own custom backend).

The **API** section lets you generate secure API tokens that allow those systems to send and receive data from MagicBlocks.

This is especially useful if you want to:

-   Send contacts from MagicBlocks into your CRM
-   Trigger automation workflows when a goal is completed
-   Build dashboards that monitor your AI’s performance
-   Sync user events or form submissions to external systems

Think of your API token as your Agent’s passport. No passport, no travel outside the platform.  

## Before You Go Live: Test the API Connection

Just like you test your Agent’s messaging flow before publishing, you should test your API connection to make sure data flows correctly.

### Test Checklist

After generating a token:

**Ping the API**  
Use a tool like Postman or cURL to make a simple request.

```
curl -X GET "https://api.magicblocks.com/v1/contacts" \
-H "Authorization: Bearer YOUR_API_TOKEN"
```

If you get a valid response, congrats — your Agent just shook hands with your system.

**Send a Test Event**  
For example, send a goal completion:

```
curl -X POST "https://api.magicblocks.com/v1/goals" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
  "goal_name": "Test Goal",
  "value": 1
}'
```

Confirm it appears in your analytics or workflow destination.

**Verify Permissions**  
Make sure the system you're connecting has the correct permissions and environment variables set.

**Check Logs**  
In your integration tool (Zapier, custom app, CRM), ensure you see the test hit.

If everything works smoothly — green light for go-live.  
If not, refine, retest, and only publish when the data flow is clean.

Launching with a broken integration is like opening a restaurant with no cash register. People show up, but… no one gets seated.

## Best Practice for Launch

Start with a **single goal or contact sync** to verify the whole chain works end to end. Once confirmed, scale your automation confidently.

Pro tip:  
Label your token based on the environment, like:

`Zapier - Live`

`CRM Sync - Production`

`Testing Token (Delete After Go-Live)`

Yes, future-you will thank present-you.

## Common Go-Live API Mistakes (and how to avoid them)

Even experienced builders can run into launch hiccups. Here are the most common API mistakes we see when going live — and how to prevent them.

| Mistake | What happens | How to avoid it |
| --- | --- | --- |
| **Using a test token in production** | Data stops flowing or lands in the wrong environment | Create separate<br>**Testing**<br>and<br>**Live**<br>tokens and label them clearly |
| **Forgetting to store the token** | Token cannot be recovered and a new one must be generated | Save your token in a secure notes vault or environment variable the moment you generate it |
| **No validation before launch** | API appears connected but silently fails | Always send a test call (GET + POST) before pushing live |
| **Incorrect auth header format** | Requests rejected by server | Ensure header uses:<br>`Authorization: Bearer YOUR_API_TOKEN` |
| **Connecting automations but not mapping fields** | Contacts sync with missing or wrong data | Double-check field mapping in tools like Zapier/Make before turning on workflows |
| **Not monitoring logs** | Errors go unnoticed until a contact complains | Review logs after your first few real contacts come through |
| **Using the API token in frontend code** | Token can be exposed & misused | Store tokens in backend or automation tools only — never client-side |
| **No token expiration strategy** | Old access sitting open = security risk | Rotate tokens periodically and delete unused ones |

*Best practice: treat your API launch like a mini flight check — inspect, test, confirm, then lift off.*

## Related Articles

[Sending Contacts to CRM](https://help.magicblocks.ai/en/article/introduction-to-sending-leads-to-other-systems)  
[Adding Contacts via API](https://help.magicblocks.ai/en/article/leads-api)