> For the complete documentation index, see [llms.txt](https://docs.coherent.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coherent.global/spark-apis/getting-started.md).
# Getting started
Welcome to the Spark API documentation! We have documented the important APIs used to call and manage Spark services!
## Base URL
```shellscript
https://excel.{environment}.coherent.global
```
The environment is part of your [Login and logout](/navigation/login-and-logout.md#log-in-to-spark) URL.
## Spark object model
| | |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Folder | Folder can contain documents, services, and transform documents. For legacy v1 APIs, this may be referred to as a "product".
Actions to manage folders:
|
| Documents | Documents can be uploaded into a Folder. |
| Service | Services are created in a folder. A service is the representation of the Excel converted to code and into an API. For legacy v1 APIs, this may be referred to as an "engine".
Actions to manage services:
|
| Service versions | As changes are made to a single service, new service versions are created.
When "running" on a service, a service version needs to be resolved or targeted.
Actions to run service versions:
|
| WebAssembly module | Each service version includes code compiled from Excel into C++, then into a WebAssembly module ZIP bundle by /pages/qc2ynJ5gnthNAqVrFQRg. These bundles can be downloaded for offline execution.
Actions on Wasm ZIP bundles:
|
| API calls | When an API call is made to a service version, the request and response data is saved into the /pages/-Mbp1TWI7E1KNb9JlN0\_.
Actions to retrieve from the /pages/-Mbp1TWI7E1KNb9JlN0\_:
|
| Transform documents | Transform documents contain the instructions on how to translate requests and responses to be compatible with the Spark /pages/i1Gw4hnm5WLCg1qp8zNM.
Actions on Transform documents:
|
## Authorization
Depending on the API, there are different authentication options available:
## Compression
The following request headers are supported for compression of requests and responses.
| Key | Value |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| `Accept-Encoding` | When set to `gzip` or `br`, the API response is compressed. If using [Postman](https://www.postman.com/), this is automatically added. |
| `Content-Encoding` | When set to `gzip` or `br` or `deflate`, apply the associated compression to the request body and submit the request body in binary format. |
## OpenAPI Specification
We are working to document our APIs using the [OpenAPI Specification](https://swagger.io/specification/).
{% content-ref url="/pages/qMmEEb8vRC9bxDYOYvB8" %}
[Spark OpenAPI Specification](/spark-apis/spark-openapi-specification.md)
{% endcontent-ref %}
## Documentation scope
APIs that are not documented here may be subject to change without notice.