How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Scout RFP (Workday Strategic Sourcing) attachments API

Use the attachments API to create, update, and delete the attachments in Workday Strategic Sourcing.## Working with AttachmentsCreating attachments for Workday Strategic Sourcing objects is a two-step process. First, you need to informthe system about your intention to upload an attachment by issuing a "Create an Attachment" request,consisting of the file name and a link to the object to which you are adding an attachment. The linkis represented by a relationship object containing an object ID and its type.In the response you will receive a link in the `upload_url` attributes, along with required HTTP headersto send with your file. You will need to upload your file as a binary stream in a PUT request into thespecified URL, making sure the required headers are present. Here is how the workflow might looklike when triggered from a console:```bash$ curl -H "X-Api-Key: ${COMPANY_KEY}" \ -H "X-User-Token: ${USER_TOKEN}" \ -H "X-User-Email: ${USER_EMAIL}" \ -H "Content-Type: application/vnd.api+json" \ -X POST \ -d ' { "data": { "type": "attachments", "attributes": { "title": "My Interesting Document", "file_name": "Some Interesting File.pdf" }, "relationships": { "contract": { "data": { "id": 1, "type": "contracts" } } } } } ' \ "https://api.us.workdayspend.com/services/attachments/v1/attachments"{ "data": { "id": "1", "type": "attachments", "attributes": { "title": "My Interesting Document", "file_size": null, "upload_url": "https://upload.s3.amazonaws.com/uploads/contract/1/hex/file.pdf?some=very&long=url", "upload_headers": [ { "name": "Content-Type", "value": "application/octet-stream" }, { "name": "x-amz-acl", "value": "private" }, { "name": "x-amz-server-side-encryption", "value": "AES256" }, { "name": "Content-Disposition", "value": "attachment" } ] } }}$ curl -X PUT \ --data "@file.pdf" \ -H "Content-Type: application/octet-stream" \ -H "x-amz-acl: private" \ -H "x-amz-server-side-encryption: AES256" \ -H "Content-Disposition: attachment" \ https://upload.s3.amazonaws.com/uploads/contract/1/hex/file.pdf?some=very&long=url```The upload URL expires within 15 minutes after issuing. Please note that you will not be able to uploadthe data file to the attachment object after that. An automated system will purge all partial uploadsafter a certain period (usually within 30-60 minutes after creation) to prevent orphan records fromoverflowing the system.**Please Note**: The list of headers and their values might change at any time, so when you'reimplementing an integration with the Workday Strategic Sourcing system, make sure to include all of the HTTP headersreturned from the attachments endpoint.## Attachment Object

Scout RFP (Workday Strategic Sourcing) attachments API is one of 46 APIs that Scout RFP (Workday Strategic Sourcing) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Attachments. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 6 operations across 3 paths, and defines 30 schemas. It is described by OpenAPI 3.0.2, at version 1.0.

Requests are made against 2 base URLs: https://api.us.workdayspend.com/services/attachments/v1, https://api.sandbox.us.workdayspend.com/services/attachments/v1.

6 operations 3 paths 30 schemas 3 GET2 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
1.0
Base URL
https://api.us.workdayspend.com/services/suppliers/v1
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Scout RFP (Workday Strategic Sourcing) attachments API declares 3 security schemes for authenticating requests. An API key is passed in the header as X-Api-Key (api_key). An API key is passed in the header as X-User-Token (user_token). An API key is passed in the header as X-User-Email (user_email). By default, every request must be authenticated.

  • api_key — Company API key.
  • user_token — User token.
  • user_email — User email.

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 3 GET, 2 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

attachments 6

Use the attachments API to create, update, and delete the attachments in Workday Strategic Sourcing. Working with Attachments Creating attachments for Workday Strategic Sourcing o…

GET
/attachments
List Attachments
List Attachments 1 param → 200401
POST
/attachments
Create an Attachment
Create an Attachment body → 201401
GET
/attachments/{id}
Get an Attachment
Get an Attachment 1 param → 200401404
PATCH
/attachments/{id}
Update an Attachment
Update an Attachment 1 param body → 200401404409
GET
/attachments/{external_id}/external_id
Get an Attachment by External ID
Get an Attachment by External ID 1 param → 200401404
PATCH
/attachments/{external_id}/external_id
Update an Attachment by External ID
Update an Attachment by External ID 1 param body → 200401404409

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are AttachmentAttributesBase (4 properties), AttachmentCreate (3 properties), AttachmentUpdate (3 properties), ContractBase (2 properties). Each schema is shown below with its type and property counts.

AttachmentContractRelationship
object
Contract relationship.
1 property 1 required
EventBase
object
2 properties 2 required
AttachmentId
integer
Attachment identifier string.
Attachment
ProjectId
integer
Project identifier string.
AttachmentAttributesBase
object
Attachment attributes.
4 properties
EventType
string
Object type, should always be events.
ContractBase
object
2 properties 2 required
AttachmentAttributesExtended
AttachmentCreate
object
3 properties 1 required
ProjectType
string
Object type, should always be projects.
AttachmentUpload
AttachmentAttributes
AttachmentProjectRelationship
object
Project relationship.
1 property 1 required
Error
object
1 property
AttachmentUploadAttributes
SupplierCompanyId
integer
Supplier company identifier string.
ContractTypeValue
string
Object type, should always be contracts.
AttachmentBase
object
2 properties 2 required
AttachmentType
string
Object type, should always be attachments.
ProjectBase
object
2 properties 2 required
SupplierCompanyBase
object
2 properties 2 required
AttachmentUpdate
object
3 properties 2 required
AttachmentEventRelationship
object
Event relationship.
1 property 1 required
SupplierCompanyType
string
Object type, should always be suppliercompanies.
AttachmentSupplierCompanyRelationship
object
Supplier Company relationship.
1 property 1 required
ContractId
integer
Contract identifier string.
Errors
object
1 property
EventId
integer
Event identifier string.
AttachmentInputFilter
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scoutrfp-attachments-api-openapi.yml Raw ↑

Other APIs Scout RFP (Workday Strategic Sourcing) publishes across the network.

Scout RFP (Workday Strategic Sourcing) award_line_items API
Scout RFP (Workday Strategic Sourcing) awards API
Scout RFP (Workday Strategic Sourcing) bid_line_items API
Scout RFP (Workday Strategic Sourcing) bids API
Scout RFP (Workday Strategic Sourcing) contact_types API
Scout RFP (Workday Strategic Sourcing) contract_milestone_reports API
Scout RFP (Workday Strategic Sourcing) contract_reports API
Scout RFP (Workday Strategic Sourcing) contract_types API
Scout RFP (Workday Strategic Sourcing) contracts API
Scout RFP (Workday Strategic Sourcing) discovery API
Scout RFP (Workday Strategic Sourcing) event_reports API
Scout RFP (Workday Strategic Sourcing) event_supplier_companies API
Where this information came from

This is an independent, third-party profile of Scout RFP (Workday Strategic Sourcing) attachments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.