This release introduces a public Changelog, adds client-scoped webhook management endpoints, and simplifies authentication so that JWT is the primary credential used for API operations.
Impact: You can track API and documentation changes in one place, with daily release notes.
Action required: None.
References: Changelog home
Impact: You can manage webhooks per client (list, create, retrieve, update, delete) using client-scoped endpoints.
Action required: Prefer the client-scoped endpoints for all webhook operations.
References:
GET /v1/clients/{clientId}/webhooks— list webhooks for a clientPOST /v1/clients/{clientId}/webhooks— create a webhook for a clientGET /v1/clients/{clientId}/webhooks/{id}— retrieve a webhookPATCH /v1/clients/{clientId}/webhooks/{id}— update a webhookDELETE /v1/clients/{clientId}/webhooks/{id}— delete (soft-delete) a webhook
Impact: Webhooks can be partially updated (e.g., url, token, webhook_status, optional auth_* fields).
Action required: When updating a webhook, send only the fields you want to change.
References: PATCH /v1/clients/{clientId}/webhooks/{id}
Impact: x-api-key is now bootstrap-only (used to obtain a JWT). After a JWT is issued, API calls should use only Authorization: Bearer <JWT>.
Action required: Stop sending x-api-key on operational API calls; keep it only for JWT bootstrap flows.
References: POST /v1/clients/{clientId}/auth/credential-tokens
Impact: The CEP webhook is triggered only for Penny Validation transactions (amount = 0.01 MXN). INITIALIZED may appear on API reads but is not emitted by the CEP webhook and should be treated as PENDING.
Action required: Ensure your CEP webhook consumer does not expect INITIALIZED events; treat API-read INITIALIZED as PENDING.
References: /products/fincore/guides/penny_validation
Impact: POST /v1/webhooks is deprecated in favor of the client-scoped endpoint.
Action required: Migrate to POST /v1/clients/{clientId}/webhooks.
References: POST /v1/clients/{clientId}/webhooks
JWT-first auth
- Use
x-api-keyto obtain a JWT. - Use
Authorization: Bearer <JWT>for all subsequent API calls.
- Use
Webhook creation
- If you used
POST /v1/webhooks, migrate to:POST /v1/clients/{clientId}/webhooks
- If you used