Quickstart
This guide walks you through making your first API call — from obtaining an API key to fetching contacts from a connected CRM.Prerequisites
You’ll need an API key (sk_live_* or sk_test_*) from the RouteMCP dashboard. If you don’t have one yet, sign up at the dashboard and generate a key from the API Keys page.
1. Connect a Provider
Your end users need to authorize their CRM account before you can access their data. Create a connect token from your backend and use it to launch the Connect widget in their browser.| Parameter | Required | Description |
|---|---|---|
endUserId | Yes | Your system’s unique ID for this end user |
endUserDisplayName | No | Display name for the end user |
endUserEmail | No | Email address of the end user |
2. Fetch Contacts
Once a provider is connected, fetch contacts through the unified API. TheendUserId query parameter is required on all resource endpoints — it identifies which end user’s connections to query:
provider parameter:
3. Create a Contact
To write data, specify whichprovider to create the record in:
4. Work with Other Resources
The same pattern applies to all supported resource types. All endpoints require theendUserId query parameter, and write operations require provider:
contact, lead, deal, meeting
Read-only resources: owner — list and get only, cannot be created or modified.
Next Steps
- Authentication — API key types, environments, and best practices
- Connect Widget — Embed the provider authorization flow
- Field Mappings — Understand how provider data maps to the unified schema
- Error Codes — Handle errors gracefully
- API Reference — Full endpoint reference