Mokapen API Documentation

Organizations

Most Mokapen API endpoints are scoped to a single organization. The organization context is defined both in the URL and in the access token.

Organization ID in the URL

Entity endpoints follow this pattern:

GET /api/v1/{org_id}/contacts
GET /api/v1/{org_id}/tasks
POST /api/v1/{org_id}/store_contact
Replace {org_id} with the numeric organization ID. Some integrations may use an encrypted organization identifier; the API accepts both formats where supported.

Token organization binding

Access tokens issued for developer applications include an organization_id (stored in the token record and available in the OAuth token response).

When you call an endpoint with {org_id} in the URL, Mokapen verifies that the token is authorized for that organization. If the URL organization does not match the token organization, the API returns 403 Forbidden.

  • Private apps — the organization is set automatically when you generate a token (based on your active organization in the Developer dashboard).
  • Public apps — the end user selects the organization during the OAuth consent step.

Organization list endpoint

To retrieve organizations accessible to the authenticated user or integration:

GET /api/v1/organizations

Organization premium & API access

API availability and daily quotas depend on the organization's Mokapen subscription plan. See Rate Limits for plan-based daily limits.

Začnite delati in prihranite čas.

ali
Rezerviraj predstavitev

Potrebujete pomoč?