> ## Documentation Index > Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt > Use this file to discover all available pages before exploring further. # Get CRM context for a contact > Returns a normalised, cross-CRM overlay for a single contact — linked records, deals/opportunities, recent activity, e-commerce orders and per-provider lifetime value — aggregated across every CRM the contact is linked to (HubSpot, Salesforce, Pipedrive, Zendesk, Intercom, Shopify, WooCommerce). One provider being slow or down never blanks the others: each provider's outcome is reflected in a per-provider `sections[].status`. Powers the Inbox conversation "CRM Context" panel. Requires `contacts:read` (or `contacts:write`) scope; `viewer`-tier callers are rejected because the overlay can carry pipeline/deal-value data above their read scope. ## OpenAPI ````yaml /openapi.yaml get /api/v1/contacts/{id}/crm-context openapi: 3.1.0 info: title: Devotel CPaaS API description: Orbit by Devotel — Communications Platform as a Service API version: 1.0.0 contact: name: Devotel url: https://devotel.io email: support@devotel.io license: name: Proprietary servers: - url: https://api.orbit.devotel.io description: Production security: - Bearer: [] - ApiKey: [] tags: - name: Messages description: >- Send and manage messages across all channels (SMS, WhatsApp, RCS, Email, Viber, etc.) - name: Agents description: AI agent creation, configuration, and execution - name: Voice description: Voice calls, IVR, conferencing, and SIP trunking - name: Webhooks description: Webhook endpoint management and delivery logs - name: Numbers description: Phone number search, provisioning, and configuration - name: Contacts description: Contact management, segmentation, and lifecycle tracking - name: Campaigns description: Marketing campaign orchestration and analytics - name: Flows description: Automation flow builder and execution engine - name: Templates description: Message template management and approval workflows - name: Settings description: Organization, channel, and user preference settings - name: Verify description: OTP generation and verification across channels - name: Push description: Push notification delivery via FCM and APNs - name: Telegram description: >- Telegram bring-your-own-bot channel: connect a bot, verify a chat against the shared sandbox bot, and read unified channel state. Production sends go through the Messaging API. - name: USSD description: >- Menu-driven USSD for feature phones: define a menu tree, simulate session steps, and host the tenant-scoped aggregator callback. - name: Integrations description: Third-party service connections and OAuth management - name: Files description: >- Server-to-server media upload, listing, retrieval, and deletion (signed-URL backed) - name: Messaging Services description: >- Twilio MessagingService-parity containers bundling sender pool, opt-out list, inbound webhook, and sticky-sender/geomatch flags - name: Sender Pools description: >- Group sending numbers into pools with a selection strategy (sticky / round-robin / random) for outbound sends - name: Opt-Out Lists description: >- Per-list STOP / HELP / START keyword sets and auto-response copy (Twilio Advanced Opt-Out parity) - name: SMPP description: Tenant BYO-SMPP bind credentials and upstream termination carriers - name: Commerce description: >- Unified omnichannel conversational-commerce: cart/checkout state machine, cross-channel payment reconciliation, hosted pay-by-link, native WhatsApp checkout, and agentic-checkout payment mandates - name: Orby description: >- In-dashboard Orby operator assistant: streamed assistant turns, conversation threads, product knowledge-base search, and the tool-action approval gate. Available to signed-in operators only (dashboard session auth — API-key requests are rejected). paths: /api/v1/contacts/{id}/crm-context: get: tags: - Contacts summary: Get CRM context for a contact description: >- Returns a normalised, cross-CRM overlay for a single contact — linked records, deals/opportunities, recent activity, e-commerce orders and per-provider lifetime value — aggregated across every CRM the contact is linked to (HubSpot, Salesforce, Pipedrive, Zendesk, Intercom, Shopify, WooCommerce). One provider being slow or down never blanks the others: each provider's outcome is reflected in a per-provider `sections[].status`. Powers the Inbox conversation "CRM Context" panel. Requires `contacts:read` (or `contacts:write`) scope; `viewer`-tier callers are rejected because the overlay can carry pipeline/deal-value data above their read scope. parameters: - schema: type: string minLength: 1 maxLength: 200 in: path name: id required: true description: Contact identifier. - name: X-Test-Mode in: header required: false description: >- Sandbox opt-in for Clerk-session-authenticated requests. Set to `true` to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response `meta.test_mode: true`. **Ignored for live API keys (`dv_live_sk_*`)** — server-to-server clients must use a test-prefixed key (`dv_test_sk_*`) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header. schema: type: string enum: - 'true' - 'false' responses: '200': description: Normalised cross-CRM context envelope. content: application/json: schema: type: object description: Normalised cross-CRM context envelope. properties: data: type: object additionalProperties: true description: The aggregated cross-CRM overlay. properties: links: type: array description: One row per linked CRM record. items: type: object additionalProperties: true properties: provider: type: string enum: - hubspot - salesforce - pipedrive - zendesk - intercom - shopify - woocommerce external_id: type: string record_type: type: string record_url: type: - 'null' - string status: type: string enum: - ok - timeout - unauthorized - not_found - rate_limited - not_configured - not_supported - failed message: type: string deals: type: array description: Cross-provider deals / opportunities. items: type: object additionalProperties: true properties: provider: type: string enum: - hubspot - salesforce - pipedrive - zendesk - intercom - shopify - woocommerce deal_id: type: string name: type: - 'null' - string stage: type: - 'null' - string amount: type: - 'null' - number currency: type: - 'null' - string close_date: type: - 'null' - string url: type: - 'null' - string activities: type: array description: Cross-provider recent activity timeline. items: type: object additionalProperties: true properties: provider: type: string enum: - hubspot - salesforce - pipedrive - zendesk - intercom - shopify - woocommerce activity_id: type: string type: type: string summary: type: - 'null' - string occurred_at: type: string format: date-time direction: type: - 'null' - string description: '`inbound`, `outbound`, or null.' orders: type: array description: E-commerce order history (Shopify / WooCommerce). items: type: object additionalProperties: true properties: provider: type: string enum: - hubspot - salesforce - pipedrive - zendesk - intercom - shopify - woocommerce order_id: type: string total: type: - 'null' - number currency: type: - 'null' - string status: type: - 'null' - string placed_at: type: - 'null' - string url: type: - 'null' - string lifetime_value: type: array description: >- Per-provider lifetime-value rollups. Currency is NOT cross-normalised — each entry is in its provider's native currency. items: type: object additionalProperties: true properties: provider: type: string enum: - hubspot - salesforce - pipedrive - zendesk - intercom - shopify - woocommerce currency: type: string total: type: number order_count: type: integer sections: type: array description: >- Per-provider request outcome — drives the FE per-card error/empty states. items: type: object additionalProperties: true properties: provider: type: string enum: - hubspot - salesforce - pipedrive - zendesk - intercom - shopify - woocommerce status: type: string enum: - ok - timeout - unauthorized - not_found - rate_limited - not_configured - not_supported - failed message: type: string duration_ms: type: integer retry_after_seconds: type: integer generated_at: type: string format: date-time description: Server clock at envelope assembly. meta: type: object properties: request_id: type: string description: >- Unique request identifier (also returned in X-Request-Id header) timestamp: type: string format: date-time description: ISO 8601 UTC timestamp of the response '400': $ref: '#/components/responses/StandardError' '401': $ref: '#/components/responses/StandardError' '403': $ref: '#/components/responses/StandardError' '404': description: Not found — no resource matches the supplied identifier. content: application/json: schema: type: object properties: error: type: object required: - code - message - status properties: code: type: string description: >- Machine-readable error code (e.g. INVALID_PHONE_NUMBER) message: type: string description: Human-readable error description status: type: integer description: HTTP status code details: type: object additionalProperties: true description: Additional context about the error meta: type: object properties: request_id: type: string timestamp: type: string format: date-time docs_url: type: string format: uri description: Link to relevant error documentation '422': description: >- Unprocessable entity — the request was well-formed but semantically invalid. content: application/json: schema: type: object properties: error: type: object required: - code - message - status properties: code: type: string description: >- Machine-readable error code (e.g. INVALID_PHONE_NUMBER) message: type: string description: Human-readable error description status: type: integer description: HTTP status code details: type: object additionalProperties: true description: Additional context about the error meta: type: object properties: request_id: type: string timestamp: type: string format: date-time docs_url: type: string format: uri description: Link to relevant error documentation '429': $ref: '#/components/responses/RateLimitedResponse' '500': $ref: '#/components/responses/StandardError' components: responses: StandardError: description: >- Standard error envelope. `error.code` is machine-readable; see the [error reference](https://docs.orbit.devotel.io/reference/error-codes) for the catalogue. content: application/json: schema: type: object properties: error: type: object required: - code - message - status properties: code: type: string description: Machine-readable error code (e.g. INVALID_PHONE_NUMBER) message: type: string description: Human-readable error description status: type: integer description: HTTP status code details: type: object additionalProperties: true description: Additional context about the error meta: type: object properties: request_id: type: string timestamp: type: string format: date-time docs_url: type: string format: uri description: Link to relevant error documentation RateLimitedResponse: description: >- Rate limit exceeded. Wait `error.retry_after` seconds (or read the `Retry-After` header) before retrying. Returned when the request would exceed the bucket identified by `X-RateLimit-Bucket`. headers: X-RateLimit-Limit: description: Total request quota for the current window. schema: type: integer minimum: 0 X-RateLimit-Remaining: description: Requests remaining in the current window. schema: type: integer minimum: 0 X-RateLimit-Reset: description: >- Absolute unix-epoch-seconds timestamp at which the current window resets. schema: type: integer minimum: 0 X-RateLimit-Bucket: description: >- Name of the rate-limit bucket the request was bound by (e.g. `auth-write`, `money`, `agent-invoke`, or `custom:/`). Stripe-style — lets clients see which named cap they hit. schema: type: string RateLimit-Limit: description: >- draft-ietf-httpapi-ratelimit-headers no-prefix mirror of `X-RateLimit-Limit`. Some SDKs read only this form. schema: type: integer minimum: 0 RateLimit-Remaining: description: >- draft-ietf-httpapi-ratelimit-headers no-prefix mirror of `X-RateLimit-Remaining`. schema: type: integer minimum: 0 RateLimit-Reset: description: >- draft-ietf-httpapi-ratelimit-headers no-prefix mirror — delta seconds from now until the window resets (NOT epoch). schema: type: integer minimum: 0 Retry-After: description: >- RFC 7231 §7.1.3 — number of seconds the client should wait before retrying. schema: type: integer minimum: 1 content: application/json: schema: type: object properties: error: type: object required: - code - message - status - retry_after properties: code: type: string enum: - RATE_LIMITED description: >- Always `RATE_LIMITED` — the global request-limiter 429. Distinct from `RATE_LIMIT_EXCEEDED`, the live per-recipient/per-tenant/per-resource frequency-cap 429 (not retired). message: type: string status: type: integer enum: - 429 retry_after: type: integer minimum: 1 description: >- Seconds to wait before retrying. Mirrors `Retry-After` header. meta: type: object properties: request_id: type: string timestamp: type: string format: date-time docs_url: type: string format: uri securitySchemes: Bearer: type: http scheme: bearer bearerFormat: JWT description: Dashboard JWT token from Clerk ApiKey: type: apiKey name: X-API-Key in: header description: Server-to-server API key (dv_live_sk_*) ````