Troubleshooting Responsive APIs

404 "No static resource" when attaching a file to an Intake

When you call the Attach file to Intake (Upload document to Intake) endpoint, the request fails with a 404 response similar to:

{
  "type": "about:blank",
  "title": "Not Found",
  "status": 404,
  "detail": "No static resource rfpserver/ext/v1/intake..."
}

The Create Intake call succeeds, and your authentication and Intake ID are valid - only the file attachment step fails.

Cause

The Upload document to Intake endpoint no longer accepts files as a multipart/form-data upload. The endpoint was updated to accept file uploads in JSON format, with each file passed as a Base64-encoded string. Requests still built in the older multipart format do not match the current endpoint and return a 404.

Resolution

Update your integration to use the current request format:

1. Send the request body as JSON. Set your Content-Type to application/json and construct a JSON body instead of a multipart form.

2. Base64-encode each file. Convert the binary file to a Base64 string and pass it in the data field.

3. Use the array for multiple files. The endpoint accepts an array of files, so you can upload one or several documents in a single request.

4. Specify the file type. Set type to SOURCE or SUPPORT for each file, as needed.

For the exact field names, request structure, and a sample payload, see the Upload document to Intake endpoint in the Developer Portal.

Migrating an existing integration

If your integration was built against the earlier multipart/form-data version of this endpoint, you must update it to the JSON + Base64 format described above. No change is required to how you create the Intake - only the file attachment request needs to be updated.

Invalid collection name" (INVALID_COLLECTION_NAMES) when creating a user

When you call the Create User endpoint and include collections in the collectionList field, the request fails with an error similar to:

{
  "ERROR_MESSAGE": "INVALID_COLLECTION_NAMES_[Finance, Regional Sales, Legal - EMEA, Product (Beta), Risk & Compliance]"
}

Some collections are accepted, so the same request succeeds when you remove certain collections, while others are rejected. This happens even though every collection name is valid, exists in Responsive, and can be assigned to the user manually in the UI.

Cause

This is expected behavior of the Create User API. By design, collectionList accepts only collections that are accessible to all users during user creation. Collections restricted to specific users cannot be assigned in the Create User request and are returned in the INVALID_COLLECTION_NAMES list.

The error is not related to the collection name itself. The number of words, spaces, or special characters in the name has no effect. A collection is rejected only because its access is restricted, not because of how it is named.

Resolution

Provision users with restricted collections in two steps:

1. Create the user with the Create User API. Either omit collectionList entirely, or include only collections that are accessible to all users.

2. Assign restricted collections with the Update User API. After the user is created, call the Update User endpoint to append the restricted or permission-gated collections to the user's profile. The Update User API does not have this limitation.

For the full request format and field reference, see the Create User and Update User endpoints in the Developer Portal.