Measura API documentation · v1

Get API identity

Check the shop and API key being used by an integration, along with plan and capability information.

Code example

GET /api/v1/me

Headers:
  Authorization: Bearer <api-key>

Response example (200 success)

Code example

{
  "success": true,
  "data": {
    "shop": "example.myshopify.com",
    "plan": "Enterprise",
    "keyId": "example-key-id",
    "capabilities": {
      "publicApi": true,
      "orderEdit": true,
      "inventory": true,
      "pricingRules": false
    }
  },
  "error": null
}

Response fields

Scroll horizontally to see all columns.

Field	Type	Description
`data.shop`	string	Authenticated Shopify shop domain.
`data.plan`	string \| null	Current active subscription name, or null when unavailable.
`data.keyId`	string	Identifier of the authenticated public API key; the secret is never returned.
`data.capabilities.publicApi`	boolean	Whether the plan supports Public API access.
`data.capabilities.orderEdit`	boolean	Whether the plan supports the order-edit feature. This is not the ORDER_EDIT add-on activation check performed by measured order write routes.
`data.capabilities.inventory`	boolean	Whether the plan supports Measura inventory.
`data.capabilities.pricingRules`	boolean	Whether the Pricing Rules add-on is active. When no add-on state exists, a legacy nonempty customer-tag registry also enables this flag.
`error`	null	Null for a successful response.

Error responses

Scroll horizontally to see all columns.

Status code	Description
401 / 403 / 429	Authentication, Public API entitlement, or rate-limit failure.
500	Failed to fetch API identity.

Note

This endpoint uses the same Public API authentication and entitlement checks as other routes. Responses return Cache-Control: private, max-age=60. Capabilities describe the fields listed above; individual endpoints still validate their own required add-ons, resource eligibility, and request conditions.