Field attachments reference

Field attachments endpoint authentication, parameters, request and response contracts.

Last updated: 10 November 2026

Paths, methods, parameters and available schemas are generated from the OpenAPI document in the repository.

Note: These endpoints form the browser application contract and do not provide the same versioning assurance as v1. Use the versioned API for external integrations.

GET /api/p/{pid}/ekler

List attachments

Authentication: User session (cookie). Scope: Relevant organisation/project membership and operation permission; writes also check the current role, module and licence permissions.

Parameters

Responses

HTTP 200

application/json

This OpenAPI document does not define a body schema. See the relevant developer guide for details.

HTTP 422

application/json

For error meanings and client actions, see the error code glossary.

POST /api/p/{pid}/ekler/{eid}/dosya

Upload attachment file

Authentication: User session (cookie). Scope: Relevant organisation/project membership and operation permission; writes also check the current role, module and licence permissions.

Parameters

Request body

multipart/form-data

Responses

HTTP 200

application/json

This OpenAPI document does not define a body schema. See the relevant developer guide for details.

HTTP 422

application/json

For error meanings and client actions, see the error code glossary.

GET /api/p/{pid}/ekler/{eid}/dosya

Download attachment file

Authentication: User session (cookie). Scope: Relevant organisation/project membership and operation permission; writes also check the current role, module and licence permissions.

Parameters

Responses

HTTP 200

application/json

This OpenAPI document does not define a body schema. See the relevant developer guide for details.

HTTP 422

application/json

For error meanings and client actions, see the error code glossary.