Getting started
- A company administrator opens Empresa › Integraciones in the application (the application is in Spanish) and creates an integration.
- The administrator grants authorized data by domain and field group. The
confidentialandpeoplegroups require explicit confirmation. - For webhooks, create a destination with an HTTPS URL and copy the signing secret, which is shown only once. For the API, create an OAuth 2.0 client or an API key.
- Send the test event, verify the signature at the receiver and activate the destination.
Permissions belong to the company and can be revoked at any time; on revocation the API responds 403 immediately and pending deliveries are cancelled.
Reference
| Section | Content |
|---|---|
| Webhooks | Envelope, headers, signature, retries, ordering, idempotency and authentication toward your receiver. |
| Data API | OAuth 2.0 tokens, scopes, resources, cursor pagination, quotas and errors. |
| Event catalog | Each event type, its domain and its JSON Schema. |
| System guides | SAP Integration Suite, MuleSoft, Boomi, Azure Logic Apps, Power Automate, Dynamics 365, Salesforce, HubSpot, n8n, Make, Zapier, and signature verification in Node.js, Python, Java and C#. |
| Errors | One document for each API error code. |
| Security | Security evaluation package, with a downloadable PDF. |
URLs that Masnet emits
The following addresses appear in deliveries and API responses and resolve to this documentation:
| Where it appears | Address |
|---|---|
dataschema member of the envelope | https://masnet.com/developers/schemas/<object>/v1.json |
| Envelope schema | https://masnet.com/developers/schemas/envelope/v1.json |
type member of an error | https://masnet.com/developers/errors/<code> |
User-Agent header of webhooks | Masnet-Webhooks/1.0 (+https://masnet.com/developers/webhooks) |
Versions and compatibility
- The major version appears in the event type (
.v1), in the API path (/v1) and in the schemas. - Within a major version the following are compatible: new optional fields, new event types and new values in open enumerations. Write your receiver to ignore what it does not know.
- An incompatible change creates a new major version that is published in parallel.
Support and contact
For technical questions write to [email protected] and include the correlation_id of the response or the webhook-id of the event. Report vulnerabilities to [email protected], according to Annex B of the Complementary Annexes (published in Spanish).