Get evidence by id

Request

Returns one evidence for the authenticated account, in the same shape as an item of the /v2/evidences list.

Security

ApiToken

Path

idstring^[0-9a-fA-F]{24}$required

Bagel ObjectId of the evidence.

GET

/v2/evidences/{id}

curl -i -X GET \
  'https://api.bagel.ai/v2/evidences/{id}' \
  -H 'authorization: YOUR_API_KEY_HERE'

Responses

The evidence

Bodyapplication/json

idstring

Unique Bagel ID for the evidence

Example:"evid123"

titlestring

The title of the evidence

Example:"Evidence for Compliance"

originstring

The true source system this evidence came from (can be Bagel or external apps like Salesforce, Zendesk, etc.). When the evidence was ingested through an intermediary transport (e.g. a Zendesk ticket synced via Snowflake), this reflects Zendesk, not Snowflake — see via for the transport.

Example:"System"

viastring or null

The transport origin was reported as before being resolved to the true source system. Set only when the evidence (or its origin cx item) carries a trueOrigin distinct from origin — e.g. a Zendesk ticket ingested via a Snowflake connection reports origin: "zendesk", via: "snowflake". Null when origin already reflects the real source system.

Example:"snowflake"

origin_idstring or null

The ID of the item this evidence originated from in the external system.

Prefers the evidence's own external ID, which is set when an integration created it directly against an external record. Most evidence is instead derived from a conversation, ticket or call that Bagel ingested and carries no ID of its own — in that case this falls back to origin_object.origin_id, the ID of the source item.

Null only when neither is available (for example evidence submitted through the Chrome extension with no external source item).

Example:"orig5678"

descriptionstring

The description of the evidence

Example:"Supporting evidence for compliance case."

prioritystring

The priority of the evidence, usually set to default and can be selected when evidences are created from GTM apps

Example:"Medium"

domainstring

Broad business domains that are often connected to several product areas. These represent the main domains of the company.

Example:"Legal"

product_areastring

More specific area of the business product related to the idea

Example:"Risk Management"

product_sub_areastring

Further refines the product categorization

Example:"Fraud Detection"

typestring or null

The type of evidence. Can be either 'gap' or 'request'.

'gap': Evidence automatically extracted from various data sources such as:
- Support calls and interactions
- Customer surveys
- Customer feedback
- And other customer touchpoint data These represent identified gaps.
'request': Evidence created and submitted primarily by GTM teams using their apps (Salesforce, Zendesk) or created inside Bagel platform by Bagel users.

Enum:"gap""request"null

Example:"request"

statusstring or null

The status of the evidence. Possible states:

'inReview': The evidence request is waiting for review
'assigned': The evidence has been assigned to idea
'dismissed': The evidence request has been dismissed/rejected
null: state for 'gap' evidence

Enum:"inReview""assigned""dismissed"null

Example:"inReview"

status_infoobject

Export API workflow status: lifecycle summary (comma-separated external labels using the same alias rules as Customer 360) and assigned idea id from evidence.ideaId.

business_namestring

The business name of the evidence

Example:"Acme Corp"

sourcestring

The source of the evidence

Example:"Internal Audit"

ownerobject

A Bagel user who is set as the owner of this evidence. Ownership is typically assigned automatically based on the evidence's product area - each product area in Bagel settings has a designated owner, and when evidence is created or assigned to a product area, its owner is set to match that area's owner.

delivery_itemobject or null

External item (usually a Jira issue) inherited from the idea the evidence is assigned to (ideaId). It mirrors that idea's delivery_item. Null when the evidence has no assigned active idea, or the idea has no linked delivery item. An idea reached only through gtm_idea does not contribute a delivery item.

origin_objectobject

gtm_ideaobject

Represents an idea that was suggested by the GTM team during evidence submission. When GTM teams submit evidence through their apps (like Salesforce or Zendesk), they can suggest an existing idea that this evidence should be connected to. This is different from a direct idea connection and serves as a suggestion that can be reviewed by the evidence owner.

submitterobject

Information about the user who submitted the request. Only present for evidence of type 'request'. Not applicable for evidence of type 'gap'.

companyobject

The company/account linked to this evidence. The connection is established differently based on evidence type and origin:

For Salesforce submissions: Automatically set based on the account from which the evidence was submitted
For Zendesk/Chrome extension: Manually set during submission
For 'gap' type evidence: Set to the account connected to the item from which the gap was extracted

Company IDs from different systems are stored to maintain proper linking across integrations. Currently supports Salesforce and Zendesk as primary sources.

reject_infoobject

Information about the rejection of an evidence request. This is only present when a GTM-submitted evidence has been rejected by a Product Manager during the review process. This helps track why and by whom the evidence request was rejected.

createdAtstring, (date-time)

The creation date of the evidence

Example:"2023-12-01T10:00:00.000Z"

updatedAtstring, (date-time)

The last updated date of the evidence

Example:"2023-12-05T15:00:00.000Z"

Response

{
  "id": "evid123",
  "title": "Evidence for Compliance",
  "origin": "System",
  "via": "snowflake",
  "origin_id": "orig5678",
  "description": "Supporting evidence for compliance case.",
  "priority": "Medium",
  "domain": "Legal",
  "product_area": "Risk Management",
  "product_sub_area": "Fraud Detection",
  "type": "request",
  "status": "inReview",
  "status_info": {
    "processed_status": "Pending, Roadmap, GA",
    "assigned_idea_id": "6818c2100e46cea9d81234556"
  },
  "business_name": "Acme Corp",
  "source": "Internal Audit",
  "owner": {
    "id": "owner123",
    "name": "John Smith",
    "email": "john.smith@example.com"
  },
  "delivery_item": {
    "id": "delivery567",
    "origin": "jira",
    "origin_id": "JIRA-123",
    "title": "2FA Implementation",
    "description": "Implement 2FA for all users with support for Google Authenticator, Microsoft Authenticator, and SMS. should support setting policy for different roles.",
    "status": "Completed",
    "link": "https://delivery.example.com/item/567"
  },
  "origin_object": {
    "id": "12345",
    "origin": "salesforce",
    "origin_id": "sFOpportunity123",
    "title": "Opportunity Title",
    "description": "Opportunity Description",
    "type": "opportunity",
    "link": "https://example.salforce.com/item/567"
  },
  "gtm_idea": {
    "id": "idea789",
    "status": "Implemented",
    "title": "Streamlined Workflow"
  },
  "submitter": {
    "id": "submit123",
    "name": "Alice Johnson",
    "email": "alice.johnson@example.com"
  },
  "company": {
    "external_id": "comp123",
    "name": "Tech Solutions Inc.",
    "intercom_id": "intercom567",
    "sf_id": "sf789",
    "zendesk_id": "zendesk456",
    "crm_id": "001Rt000001i4OsTQZ"
  },
  "reject_info": {
    "reason": "Insufficient data",
    "comment": "Please provide additional supporting documents.",
    "rejected_at": "2023-12-01T00:00:00.000Z",
    "rejecting_user": { … }
  },
  "createdAt": "2023-12-01T10:00:00.000Z",
  "updatedAt": "2023-12-05T15:00:00.000Z"
}