Authenticate requests to Snapshots API using API keys with the saas/location.read scope. Store credentials securely and rotate them regularly to maintain secure access between Accredible Certificates and the Snapshots API.
Configure Accredible Certificates to accept and forward data from Snapshots API via secure webhooks or API keys, ensuring only trusted sources can trigger updates.
Key endpoints used: GET /locations to verify locations; GET /certificates to retrieve certificate data; POST /certificates/{id}/sync to push updates; POST /webhooks/certificates for event-driven updates; POST /batch_sync for nightly reconciliations. Additional endpoints may be added as needed for auditing and mapping fields.
Trigger: A new certificate is issued in Accredible Certificates, prompting an immediate update to Snapshots API to reflect the credential status.
Actions: Create or update a certificate record in Snapshots API, log the event, and notify downstream systems.
Method/Path: POST /certificates/{id}/sync
Key fields: certificate_id, user_id, issue_date, location_id
Trigger: Midnight batch job to reconcile differences between Accredible Certificates and Snapshots API data.
Actions: Upsert multiple records, reconcile statuses, generate a reconciliation report.
Method/Path: POST /batch_sync
Fields: batch_id, records[]
Trigger: Accredible Certificates emits events (certificate_created, certificate_updated) via webhook.
Actions: Create/update corresponding records in Snapshots API and trigger downstream notifications.
Method/Path: POST /webhooks/certificates
Fields: event_type, certificate_id, timestamp, source
Automate data flow between systems without custom development.
Improve verification speed and accuracy for credential issuance and retrieval.
Maintain an auditable trail of changes for compliance and reporting.
This glossary covers API endpoints, triggers, actions, and data fields used to connect Accredible Certificates with the Snapshots API.
A URL path and HTTP method used to access a resource in the Snapshots API (e.g., GET /locations).
An automated message sent from Accredible Certificates to Snapshots API when an event occurs, such as certificate creation or update.
An event that starts an automation, such as a new certificate issuance or status change.
The process of proving identity to access the API (API keys, OAuth tokens).
Use a lightweight webhook to push new certificates from Accredible to Snapshots API instantly, enabling immediate status updates and downstream reporting.
Capture every change with timestamped logs, linking certificate events to user actions for easy auditing and verification.
Set up nightly batch syncing to reconcile differences and produce consolidated dashboards for management reporting.
Generate API keys with the saas/location.read scope and securely store them. Grant access only to required resources.
Configure endpoints like /locations and /certificates in Snapshots API, and set your Accredible Certificates webhook URL for event notifications.
Run test certificates, verify field mappings, and monitor logs to ensure data integrity across systems.
The integration connects Accredible Certificates with the Snapshots API to enable secure data sharing and lifecycle automation. It supports real-time updates, batch syncing, and webhook-driven event notifications. This helps ensure credential data is accurate across platforms and easy to verify.
No code is required for standard use, thanks to built-in webhooks and API key authentication. Advanced scenarios may benefit from lightweight automation rules, but the core flow can be set up without custom development.
Essential endpoints include location discovery (GET /locations), certificate data (GET /certificates), and syncing (POST /certificates/{id}/sync or POST /batch_sync). Webhook endpoints (POST /webhooks/certificates) are used for real-time updates.
Security is enforced via API keys with scoped access, encrypted transport (HTTPS), and IP allowlists. Rotate credentials regularly and monitor for unusual activity.
Data mapping should align fields like certificate_id, user_id, issue_date, and location_id. Use a mapping plan to ensure consistent data types and handle missing values gracefully.
Yes. Webhooks can push updates in real time, while batch syncing handles reconciliation at scheduled intervals. You can combine both for a robust data flow.
Audit trails appear in Snapshots API logs and Accredible Certificates activity feeds. Use the batch reports and webhook event logs for traceability.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
