Skip to main content
Get your first customer organization up and running with AI phone answering in under 5 minutes!

What You’ll Build

By the end of this guide, you’ll have:
  • ✅ An authenticated API connection
  • ✅ A customer organization created
  • ✅ A phone number provisioned with AI answering
  • ✅ An embed token to display the dashboard

Prerequisites

1

Partner Account

You need a partner account with Answering Agent. If you don’t have one, contact us to get started.
2

API Key

Sign in to your partner dashboard and generate an API key at Settings → API Keys. Copy it somewhere safe!
3

Development Environment

You can use any language or tool that makes HTTP requests. We’ll show examples in cURL, JavaScript, and Python.

Step 1: Test Your API Key

First, let’s verify your API key works by listing your organizations:
Expected Response:
An empty array is perfect! It means your API key is working and you have no organizations yet.
If you get a 401 error, double-check that your API key is correct and you’re using the X-API-KEY header (not Authorization).

Step 2: Create Your First Organization

Now let’s create an organization for a customer. We’ll create the organization and its owner user in a single API call:
Expected Response:
🎉 Great! You’ve created your first organization with an owner user. Note the organization.id - you’ll need it for the next step.
The external_id is your system’s ID for this user. Use it to link this Answering Agent user to your database. All future API calls can use this ID instead of the internal Answering Agent user ID.

Step 3: Add a Phone Number

Now let’s provision a phone number for this organization:
Expected Response:
📞 Awesome! The phone number is now active and ready to receive calls with AI answering!

Step 4: Get an Embed Token

Finally, let’s get an embed token so your customer can access their dashboard:
Expected Response:
🔑 Perfect! You now have an embed token that lets your customer access their Answering Agent dashboard.

Complete Example

Here’s the entire flow in one script:

Already-Owned Organizations: Multi-Account Viewer Flow

The quickstart above provisions organizations owned by your partner account. If your customers already own their Answering Agent organizations, use the owner-linked viewer flow instead:
  1. The customer owner accepts the partner link.
  2. The owner or an organization admin grants your partner account dashboard-viewer management.
  3. Create one identity with POST /users and an approved linked organization_id, or reuse an existing identity with PUT /organizations/{organization_id}/dashboard-viewers/{external_id}.
  4. Request GET /users/{external_id}/embed-token?organization_id={organization_id}.
  5. Put that compact token in a single /dashboard/embed iframe. Request a different scoped token and replace the iframe src when the account manager switches organizations.
The scoped viewer is organization-wide and read-only. It cannot change settings, manage members or roles, call mutation endpoints, or trigger recurring AI/model work. Detach or owner-side revocation invalidates stale scoped authority without removing access to other organizations.

What’s Next?

You’ve successfully onboarded your first customer! Here’s what you can do next:

Embed the Dashboard

Learn how to embed the Answering Agent dashboard in your application

Add More Users

Add team members to the organization

Customize AI Settings

Configure the AI agent’s behavior and responses

Explore All Endpoints

See the complete API reference

Troubleshooting

”Invalid credentials” Error

  • Double-check your API key is correct
  • Make sure you’re using the X-API-KEY header (not Authorization: Bearer)
  • Verify your partner account is active

”Organization not found” Error

  • Make sure you’re using the correct organization ID
  • Verify the organization belongs to your partner account
  • Check that the organization wasn’t deleted

Phone Number Not Provisioning

  • Ensure the area_code is valid (3 digits, US/Canada)
  • Some area codes may have limited availability
  • Try a different area code if provisioning fails

Embed Token Not Working

  • Verify the user’s external_id is correct
  • Make sure the user belongs to the organization
  • For multi-organization viewers, include the intended organization_id when requesting the token
  • Check that the owner-approved viewer grant and partner link remain active
  • Ensure the scoped relationship has not been detached or rotated

Need Help?

We’re here to help you succeed:
  • Technical Support: support@answeringagent.com
  • Documentation Issues: Report on GitHub or email support
  • Integration Questions: Our team is happy to jump on a call
Happy building! 🚀