Trigger provider projection
curl --request POST \
--url https://api.simplepay.mx/v1/customer-hub/customers/{customer_id}/provider-sync \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'Idempotency-Key: <idempotency-key>' \
--data '{}'const options = {
method: 'POST',
headers: {
'Idempotency-Key': '<idempotency-key>',
Authorization: 'Bearer <token>',
'Content-Type': 'application/json'
},
body: JSON.stringify({})
};
fetch('https://api.simplepay.mx/v1/customer-hub/customers/{customer_id}/provider-sync', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.simplepay.mx/v1/customer-hub/customers/{customer_id}/provider-sync"
payload = {}
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){}Trigger provider projection
Referencia detallada para POST /v1/customer-hub/customers//provider-sync.
POST
https://api.simplepay.mx
/
v1
/
customer-hub
/
customers
/
{customer_id}
/
provider-sync
Trigger provider projection
curl --request POST \
--url https://api.simplepay.mx/v1/customer-hub/customers/{customer_id}/provider-sync \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'Idempotency-Key: <idempotency-key>' \
--data '{}'const options = {
method: 'POST',
headers: {
'Idempotency-Key': '<idempotency-key>',
Authorization: 'Bearer <token>',
'Content-Type': 'application/json'
},
body: JSON.stringify({})
};
fetch('https://api.simplepay.mx/v1/customer-hub/customers/{customer_id}/provider-sync', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.simplepay.mx/v1/customer-hub/customers/{customer_id}/provider-sync"
payload = {}
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){}Uso
Usalo para administrar perfiles de cliente del Customer Hub (“Clientes”), el CRM tenant-scoped y agnostico de SimplePay.Antes de llamar
| Tema | Detalle |
|---|---|
| Metodo | POST |
| Ruta | /v1/customer-hub/customers/{customer_id}/provider-sync |
| Auth | Bearer API key del ambiente correcto. |
| Scope | customer_hub.provider_sync:write |
| Idempotencia | Recomendada para cualquier retry. Usa una key deterministica por operacion de negocio. |
| Guia relacionada | Customer Hub |
Patron recomendado
- Ejecuta este endpoint desde backend o job seguro, nunca desde frontend con API keys.
- Manda
Idempotency-Keycuando el endpoint cree, actualice o dispare estado. - Consulta el bloque OpenAPI de esta pagina para el shape exacto de parametros, body y respuestas.
Ejemplo minimo
terminal
curl -sS -X POST "https://api.simplepay.mx/v1/customer-hub/customers/cust_123/provider-sync" \
-H "Authorization: Bearer $SIMPLEPAY_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: sync_customer_hub_provider_v1" \
-d '{ ... }'
Errores a manejar
400indica payload, parametros o estado invalido.401o403indican API key, ambiente o scopes incorrectos.404significa que el recurso no existe para ese tenant o ambiente.409suele indicar conflicto de estado, duplicado o idempotencia incompatible.429y5xxse pueden reintentar con backoff; en writes conserva la misma idempotency key.
Contrato OpenAPI
El playground, parametros, body y respuestas de abajo salen de/openapi.json. Si el contrato cambia, actualiza la spec y regenera esta pagina.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Required string length:
8 - 255Path Parameters
Body
application/json
Customer Hub write payload. The gateway forwards the body verbatim to the owning origin Worker; consult the Customer Hub Worker contract for the exact per-operation shape.
Response
200 - application/json
Provider projection triggered
Customer Hub response object as returned by the owning origin Worker (customer, contact, address, relationship, timeline event, note, external ref, provider-sync result, link result, tag, import, sync source, or list envelope).
Last modified on July 8, 2026
⌘I