# Builds

This endpoint is used for the upload of builds

\
API URL - <https://api.moropo.com/builds>

### Available actions

1. Upload Build

## Example - Uploading a Build

Note this request uses `POST` to inform the API that a build is being uploaded

```bash
curl -X 'POST' \
  'https://api.moropo.com/builds' \
  -H 'accept: */*' \
  -H 'x-app-api-key: MOROPO_API_KEY' \
  -H 'Content-Type: multipart/form-data' \
  -F 'file=@FILE_NAME;type=application/zip'
```

Where;

* `MOROPO_API_KEY` is the API key for the target app, found in your [Moropo settings](https://app.moropo.com/settings?index=integrations).
* `FILE_NAME` is the name of the build file being uploaded. Must conform to the build file requirements laid out in [Producing an iOS Build](/uploading-your-app/producing-an-ios-build.md) and [Producing an Android Build](/uploading-your-app/producing-an-android-build.md).

#### Expected Response

```json
{
  "message": "Build created successfully.",
  "buildId": integer
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.moropo.com/ci-integration/moropo-api/builds.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.