> ## Documentation Index > Fetch the complete documentation index at: https://docs.spade.com/llms.txt > Use this file to discover all available pages before exploring further. # Get card-level trigger status > Get the status and version of the latest merchant action trigger registration at the card scope. Card-level triggers apply only to transactions for the specified card. **Important:** Triggers are only applied to enrichment responses when the status is `succeeded`. To learn more about action triggers, please read the [Merchant Action Triggers Guide](https://docs.spade.com/reference/merchant-action-triggers-guide). ## OpenAPI ````yaml /api-reference/spec.yml get /users/{userId}/cards/{cardId}/merchant-action-triggers openapi: 3.1.0 info: title: Spade API description: >- Documentation for Spade's card transaction enrichment API and related endpoints. We offer sandbox and production environments on both the east coast and west coast to enable ultra low latency enrichment for realtime applications. Each environment requires different API keys. To inquire about API keys, please contact your Spade representative or reach out to . version: 2.7.3 servers: - url: https://east.sandbox.spade.com description: East coast sandbox environment - url: https://east.api.spade.com description: East coast production environment - url: https://west.sandbox.spade.com description: West coast sandbox environment - url: https://west.api.spade.com description: West coast production environment - url: https://sandbox.v2.spadeapi.com description: East coast sandbox environment (deprecated) - url: https://v2.spadeapi.com description: East coast production environment (deprecated) - url: https://sandbox.west.v2.spadeapi.com description: West coast sandbox environment (deprecated) - url: https://west.v2.spadeapi.com description: West coast production environment (deprecated) security: - ApiKeyAuth: [] tags: - name: Card Enrichment description: Enrich card transactions - name: Transfer Enrichment description: Enrich transfers - name: Category Personalization description: Create custom categories and personalize enrichments - name: Feedback and Reporting description: Provide feedback on card events or report enrichment errors - name: Merchant Matching description: Match your merchants to Spade counterparties and locations - name: Merchant Search description: Search for Spade merchants - name: Merchant Action Triggers description: >- Register merchant action triggers and receive triggered actions in enrichment responses - name: Category Action Triggers description: >- Register category action triggers and receive triggered actions in enrichment responses paths: /users/{userId}/cards/{cardId}/merchant-action-triggers: parameters: - in: path name: userId schema: type: string maxLength: 512 description: Your unique identifier for the user required: true - in: path name: cardId schema: type: string maxLength: 512 description: Your unique identifier for the card required: true get: tags: - Merchant Action Triggers summary: Get card-level trigger status description: >- Get the status and version of the latest merchant action trigger registration at the card scope. Card-level triggers apply only to transactions for the specified card. **Important:** Triggers are only applied to enrichment responses when the status is `succeeded`. To learn more about action triggers, please read the [Merchant Action Triggers Guide](https://docs.spade.com/reference/merchant-action-triggers-guide). operationId: cardMerchantActionTriggersGet responses: '200': description: Successful operation content: application/json: schema: $ref: '#/components/schemas/ActionTriggerStatusResponse' '403': $ref: '#/components/responses/Unauthorized' '404': description: No action triggers exist for this scope content: application/json: schema: type: object properties: detail: type: string examples: - No action triggers exist for this scope '500': $ref: '#/components/responses/InternalServerError' components: schemas: ActionTriggerStatusResponse: type: object description: Response containing the status of an action trigger registration. properties: status: type: string description: > The current status of the action trigger registration. - `pending`: Registration received, processing not yet started - `running`: Registration is being processed (for batch registrations with >100 triggers) - `succeeded`: Registration complete, triggers are now active - `failed`: Registration failed, check your request and retry enum: - pending - running - succeeded - failed examples: - succeeded version: type: integer description: >- The version number of this registration. Increments with each PUT, PATCH, or DELETE request to this scope. examples: - 1 merchantTriggers: type: array description: >- The list of active merchant triggers registered for this scope. Present on GET responses; omitted on PUT and PATCH responses. items: type: object properties: id: type: string description: The trigger ID as provided during registration. examples: - merchant_123 action: type: object description: >- The action data associated with this trigger, as provided during registration. additionalProperties: true examples: - type: REWARD points: 200 totalCount: type: integer description: >- The total number of active merchant triggers registered for this scope. Present on GET responses; omitted on PUT and PATCH responses. examples: - 50000 responses: Unauthorized: description: Unauthorized content: application/json: schema: type: object properties: details: type: string examples: - Incorrect authentication credentials. InternalServerError: description: Unexpected Error content: application/json: schema: type: object properties: details: type: string examples: - Internal server error. securitySchemes: ApiKeyAuth: type: apiKey name: X-Api-Key in: header ````