generated: '2026-08-13' method: searched source: https://github.com/agilecrm/rest-api/blob/master/README.md (field tables) + openapi/*.yml (path structure) description: >- Entity/relationship graph for the Agile CRM REST API. Entities and their fields are read from the vendor's own published field tables; relationships are read from the id-reference fields in those tables (contact_company_id, contact_ids, contact_json, contacts, notes, owner_id, pipeline_id) and corroborated by the nested path structure of the documented endpoints. Agile CRM publishes no JSON Schema and no component schemas, so nothing here is derived from a schema document. identifiers: style: numeric type: Long prefixed: false note: >- Ids are bare 16-digit App Engine datastore integers (e.g. 5667649732214784) with no type prefix, so an id alone does not reveal which entity it belongs to. They are frequently returned as JSON strings inside reference arrays (contact_ids: ["122", 145, 201]) and as numbers elsewhere — the same field mixes both types in the vendor's own example payloads. timestamps: format: epoch-seconds fields: - created_time - updated_time - due - start - end note: All time fields are integer epoch seconds, not ISO 8601. entities: - name: Contact api: Contacts read_only_fields: - id - campaignStatus - unsubscribeStatus - emailBounceStatus fields: - name: id type: Long read_only: true - name: type type: String enum: [PERSON, COMPANY] default: PERSON note: The SAME entity carries both contacts and companies, discriminated by this field. - name: tags type: List note: Not applicable to companies. Tag name must start with a letter; only underscore and space are allowed as specials. - name: lead_score type: Integer note: Not applicable to companies. - name: star_value type: Short range: 0-5 - name: contact_company_id type: Long reference: Contact note: Points at another Contact whose type is COMPANY. - name: properties type: List required: true note: first_name is mandatory. - name: campaignStatus type: List