Agile CRM Notes API - API Evangelist enrichment overlay

overlay: 1.0.0
info:
  title: Agile CRM Notes API - API Evangelist enrichment overlay
  version: 1.0.0
extends: ../openapi/agile-crm-notes-api-openapi.yml
x-generated: '2026-08-13'
x-method: generated
x-source: https://github.com/agilecrm/rest-api/blob/master/README.md
x-note: 'Captures the enrichments API Evangelist applied on top of the base document: stable operationIds (the vendor names
  none), the error statuses documented in prose but absent from any machine-readable artifact, and the XML-by-default content-negotiation
  trap. It does NOT capture the path corrections made on 2026-08-13, which were applied to the base document itself because
  the previous paths did not match the vendor documentation and were therefore wrong, not enhanced.'
actions:
- target: $.info
  description: Record that this document is maintained by API Evangelist from the vendor's published REST API documentation,
    and that Agile CRM publishes no OpenAPI of its own.
  update:
    x-apievangelist-source: https://github.com/agilecrm/rest-api/blob/master/README.md
    x-provider-publishes-openapi: false
- target: $.paths['/api/contacts/email/note/add'].post
  description: Assign a stable operationId; the vendor's documentation names no operation identifiers.
  update:
    operationId: addNoteByEmail
- target: $.paths['/api/contacts/notes/bulk'].post
  description: Assign a stable operationId; the vendor's documentation names no operation identifiers.
  update:
    operationId: bulkDeleteNotes
- target: $.paths['/api/contacts/{contact_id}/notes'].get
  description: Assign a stable operationId; the vendor's documentation names no operation identifiers.
  update:
    operationId: listContactNotes
- target: $.paths['/api/contacts/{contact_id}/notes/{note_id}'].delete
  description: Assign a stable operationId; the vendor's documentation names no operation identifiers.
  update:
    operationId: deleteContactNote
- target: $.paths['/api/notes'].post
  description: Assign a stable operationId; the vendor's documentation names no operation identifiers.
  update:
    operationId: createNote
- target: $.paths['/api/opportunity/deals/notes'].post
  description: Assign a stable operationId; the vendor's documentation names no operation identifiers.
  update:
    operationId: createDealNote
- target: $.paths['/api/opportunity/deals/notes'].put
  description: Assign a stable operationId; the vendor's documentation names no operation identifiers.
  update:
    operationId: updateDealNote
- target: $.paths['/api/opportunity/{deal_id}/notes'].get
  description: Assign a stable operationId; the vendor's documentation names no operation identifiers.
  update:
    operationId: listDealNotes
- target: $.paths['/api/contacts/email/note/add'].post.responses
  description: Add the error statuses the vendor documents in its "Response - statuses" blocks but omits from any machine-readable
    form.
  update:
    '401':
      description: Unauthorised - the account email or REST client API key is wrong.
    '400':
      description: Bad Request - the input is in the wrong format. No field-level detail is returned.
- target: $.paths['/api/contacts/notes/bulk'].post.responses
  description: Add the error statuses the vendor documents in its "Response - statuses" blocks but omits from any machine-readable
    form.
  update:
    '401':
      description: Unauthorised - the account email or REST client API key is wrong.
    '400':
      description: Bad Request - the input is in the wrong format. No field-level detail is returned.
- target: $.paths['/api/contacts/{contact_id}/notes'].get.responses
  description: Add the error statuses the vendor documents in its "Response - statuses" blocks but omits from any machine-readable
    form.
  update:
    '401':
      description: Unauthorised - the account email or REST client API key is wrong.
    '204':
      description: No Content - Agile CRM returns 204 rather than 404 when no matching record exists.
- target: $.paths['/api/contacts/{contact_id}/notes/{note_id}'].delete.responses
  description: Add the error statuses the vendor documents in its "Response - statuses" blocks but omits from any machine-readable
    form.
  update:
    '401':
      description: Unauthorised - the account email or REST client API key is wrong.
- target: $.paths['/api/notes'].post.responses
  description: Add the error statuses the vendor documents in its "Response - statuses" blocks but omits from any machine-readable
    form.
  update:
    '401':
      description: Unauthorised - the account email or REST client API key is wrong.
    '400':
      description: Bad Request - the input is in the wrong format. No field-level detail is returned.
- target: $.paths['/api/opportunity/deals/notes'].post.responses
  description: Add the error statuses the vendor documents in its "Response - statuses" blocks but omits from any machine-readable
    form.
  update:
    '401':
      description: Unauthorised - the account email or REST client API key is wrong.
    '400':
      description: Bad Request - the input is in the wrong format. No field-level detail is returned.
- target: $.paths['/api/opportunity/deals/notes'].put.responses
  description: Add the error statuses the vendor documents in its "Response - statuses" blocks but omits from any machine-readable
    form.
  update:
    '401':
      description: Unauthorised - the account email or REST client API key is wrong.
    '400':
      description: Bad Request - the input is in the wrong format. No field-level detail is returned.
- target: $.paths['/api/opportunity/{deal_id}/notes'].get.responses
  description: Add the error statuses the vendor documents in its "Response - statuses" blocks but omits from any machine-readable
    form.
  update:
    '401':
      description: Unauthorised - the account email or REST client API key is wrong.
    '204':
      description: No Content - Agile CRM returns 204 rather than 404 when no matching record exists.
- target: $.info
  description: 'Flag the XML-by-default content negotiation: an Accept: application/json header is required on EVERY call
    or the response is XML.'
  update:
    x-default-response-format: application/xml
    x-json-requires-accept-header: true