Attachment API

RESTful attachment management (requires target record to exist)

Last modified 2026-03-16

Jace Benson

Table of content
  1. Key Difference
  2. Endpoints
  3. Upload Request
  4. Upload via Multipart
  5. Query Parameters
  6. When to Use

Docs

The Attachment API provides REST endpoints for uploading, downloading, and managing file attachments. Introduced in Geneva, this is the modern replacement for the SOAP AttachmentCreator.

Key Difference

Unlike the SOAP AttachmentCreator, the target record must exist before attaching.

Endpoints

Method Endpoint Purpose
GET /api/now/attachment List attachments
GET /api/now/attachment/{sys_id} Get attachment metadata
GET /api/now/attachment/{sys_id}/file Download attachment
POST /api/now/attachment/file Upload attachment
DELETE /api/now/attachment/{sys_id} Delete attachment

Upload Request

POST /api/now/attachment/file?table_name=incident&table_sys_id=9c573169c611228700193229fff72400&file_name=report.pdf
Content-Type: application/pdf

[binary file data]

Upload via Multipart

POST /api/now/attachment/upload
Content-Type: multipart/form-data

table_name: incident
table_sys_id: 9c573169c611228700193229fff72400
uploadFile: [binary data]

Query Parameters

When to Use