Skip to main content
Entities represent the people and companies your organization works with in Syntage. Use an entity ID to request data, start extractions, manage identifiers, assign entity tags, and review events for that person or company. An entity can be created with a name, type, optional RFC, optional identifiers, and optional datasources to start extracting. If required information is missing, Syntage returns an onboarding URL that can be used to collect the missing information from the entity.

​
How Entities Are Used

  1. Create or retrieve an entity.
  2. Store the entity ID returned by Syntage.
  3. Use the entity ID when requesting datasource records, creating extractions, listing events, assigning tags, or adding identifiers.
  4. If Syntage returns an onboardingUrl, send the entity to that URL or embed the onboarding experience in your own site.
The entity ID is stable across datasources. A single entity can be connected to SAT credentials, RPC data, RUG data, Buró de Crédito reports, Infonavit data, and more.

​
Entity IDs

Use the entity ID in new integrations: 
/entities/{entityId}
/entities/{entityId}/tax-status
/entities/{entityId}/invoices
Some older endpoints also accept RFC-based URLs for backwards compatibility. New endpoints and features are only added under entity-based URLs.

​
Example Create Request

This example creates a person entity, supplies the RFC directly, adds CURP as an additional Mexican identifier, and starts SAT extraction work. 
{
  "name": "Pedro Infante Cruz",
  "type": "person",
  "rfc": "PEIC211118IS0",
  "identifiers": [
    {
      "country": "mx",
      "identifier": "curp",
      "value": "PEIC211118HDFNRR09"
    }
  ],
  "datasources": [
    {
      "name": "sat",
      "options": {
        "period": {
          "from": "2026-01-01",
          "to": "2026-06-30"
        }
      }
    }
  ]
}

​
Example Entity

{
  "@id": "/entities/91106968-1abd-4d64-85c1-4e73d96fb997",
  "@type": "Link",
  "id": "91106968-1abd-4d64-85c1-4e73d96fb997",
  "type": "company",
  "taxpayer": {
    "@id": "/taxpayers/XAXX010101000",
    "@type": "Taxpayer",
    "id": "XAXX010101000",
    "name": "Syntage"
  },
  "tags": [
    {
      "@id": "/entity-tags/018f3f8f-4538-7bbb-b432-9e97e34a564a",
      "@type": "EntityTag",
      "id": "018f3f8f-4538-7bbb-b432-9e97e34a564a",
      "name": "Customer"
    }
  ],
  "createdAt": "2026-06-16T14:30:00.000Z",
  "updatedAt": "2026-06-16T14:30:00.000Z"
}

​
Identifiers

Identifiers store country-specific values that can be used by datasources and product workflows. Mexico currently supports:
CountryIdentifierExample
mxrfcXAXX010101000
mxcurpBADD110313HCMLNS09
Identifiers may be supplied when creating an entity or added later with the entity identifiers endpoint.

​
Entity Tags

Entity tags are organization-defined labels for grouping and filtering entities. They are useful when your integration needs to treat a set of entities the same way. Common use cases include:
Use caseExample
Extraction schedulersRun a daily invoice extraction for every entity tagged Daily invoices.
MonitoringTrack high-priority entities separately from the rest of your organization.
Filtering in SyntageFilter the entity list in the Syntage dashboard.
Segmentation in your productUse tags to build your own dashboards, review queues, or support workflows around tagged entities.
Create entity tags first, then assign them to an entity by updating the entity’s tags collection. When updating an entity’s tags, send the complete list of entity tag IRIs the entity should have. The submitted list replaces the previous assignments.