> For the complete documentation index, see [llms.txt](https://docs.hos.accessacloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hos.accessacloud.com/atreemo-api/get-started/introduction/deprecations.md).

# Deprecations

Migration guidance for deprecated Atreemo operations.

The Atreemo API reference documents supported operations only. Operations that Atreemo marks as deprecated are excluded from the OpenAPI reference. Use the supported replacements listed below.

## Excluded operations and replacements

| Excluded                         | Use instead                                                               |
| -------------------------------- | ------------------------------------------------------------------------- |
| `Contact(Deprecated)` operations | `Customer` operations                                                     |
| `Survey(Deprecated)` operations  | `SurveyApi` operations                                                    |
| `POST /api/Transaction/Post`     | `POST /api/Transaction/PostOrder`, or the `RealTimeTriggerApi` operations |

{% hint style="warning" %}
`POST /api/Transaction/Post` is deprecated and excluded. It is a different operation from `POST /api/Transaction/PostOrder`, which is supported and documented. The `RealTimeTriggerApi` operations are also supported and documented.
{% endhint %}

## How the reference was counted

| Step                                             | Count |
| ------------------------------------------------ | ----: |
| Requests in the public Atreemo Postman catalogue |   254 |
| Deprecated and authentication requests excluded  |    35 |
| Request entries included                         |   219 |
| Operations after consolidating request variants  |   217 |

Two pairs of Postman request variants describe the same operation, so each pair is documented as one shared operation:

| Postman variants                                                   | Documented as                               |
| ------------------------------------------------------------------ | ------------------------------------------- |
| `CommunicationPreference/Get` with `BrandID` and without `BrandID` | One `CommunicationPreference/Get` operation |
| `Subscription/Get` with `ExternalID` and without `ExternalID`      | One `Subscription/Get` operation            |

Removal dates for the deprecated operations are not covered by this documentation. New integrations should use the supported replacements above.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hos.accessacloud.com/atreemo-api/get-started/introduction/deprecations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.