Vendor guide
Contests and protests
How to ask for a change to a detail on an integration your company does not own, what to do when one of yours is asked about, and how to ask AEC Integrations to review an owner's decision.
Last updated 28 September 2026
A change request is how a company asks to change one detail of an integration it does not own. A protest is how it asks AEC Integrations to look again when the owner turns a request down. Both need a seat on your vendor account. Neither needs a plan. An owner deciding a request on an integration delivered through a connector does need one.
Request a change
You can ask to change a detail on any integration where one of your products is at an end and your company is not the owner. In the vendor portal, open the integration under your product to reach its own page. A field you can ask about shows Request a change beside its value, in the Overview or Integration links section. Choosing it opens the request form in Change requests, with that field already chosen. To start from a blank field instead, open Change requests and choose Request a correction.
The form asks for three things:
- what is wrong,
- what it should say, and
- why.
Choose Send request.
The fields you can ask about this way are the integration's name, description, how you get it, connection name, listing page, documentation, pricing, release stage, and owner. You can have one open request per field on each integration. To send a different value, withdraw the open one first.
Integrations delivered through a connector can be asked about too. The ones a connector product delivers to your product are listed in the Connectors section of that product's Integrations tab, each one your company does not own with Contest a field. Those have no type field, so their type cannot be changed this way. The fields there are the integration's name, mechanism name, direction, description, listing link, documentation link, pricing, maturity, and owner.
A change request is a request, not a change. While it is open, the public page keeps the value on record and does not show that one exists.
Who decides
- If the owner has claimed the integration, the owner decides.
- If nobody has claimed it, AEC Integrations decides.
- A request on the owner field always goes to AEC Integrations, even after a claim. An owner never rules on its own ownership.
- On an integration delivered through a connector, the owner decides only while it holds an active plan. Otherwise AEC Integrations decides.
- A request about an integration's type goes to AEC Integrations when the integration is delivered through a connector, or when the proposed type would make it one.
A request stays with whoever was deciding when you sent it, with two exceptions. If we end the owner's plan, its open requests on integrations delivered through a connector move to AEC Integrations. Open requests can also move to us when an accepted change makes an integration delivered through a connector. You can follow yours on the integration's own page, under Change requests, or across every product in Messages, under Field contests and then Submitted. While it is open it shows "With the owner" or "With AEC Integrations".
Updates about requests appear in the portal. We do not email them, so check the integration's page or Messages.
How a request ends
- Accepted. The proposed value replaces the one on record. When AEC Integrations accepts one on an integration nobody has claimed, the change usually arrives with the next catalogue update.
- Declined. The value on record stays. You see any note the decider added.
- Withdrawn. You can withdraw your own open request at any time, from a confirmation step so it is not sent by accident. A request also closes as withdrawn if the integration is retired, and restoring it does not reopen the request.
When your integration is asked about
Once your company has claimed an integration, requests about its details come to you on that integration's own page, under Change requests. You can also see them, across every product, in Messages under Field contests and then Received. Each one shows the value on record, the proposed value, and the reason.
- Accept writes the proposed value to the public page straight away.
- Decline leaves the value as it is. You can add a note, which the sender sees.
On an integration delivered through a connector, deciding a request needs an active plan. If we end your plan, the open ones move to AEC Integrations.
Editing a field yourself does not close a request on it. The request stays open until you decide it.
Requests sent before you claimed the integration stay with AEC Integrations.
Ask AEC Integrations to review an owner's decision
If an owner declined your request, or left it unanswered, you can ask us to review it. Open it on the integration's page or in Messages and choose Ask AEC Integrations to review.
The time limits are counted in whole days, and the portal shows each deadline:
- After a decline, you have 30 days to ask.
- If the owner has not answered, you can ask from day 30 after you sent the request until day 60.
- The owner can reply once, within 14 days of your request.
We read both sides and say which one we agree with. Our view is advice. It does not change the integration, because the owner keeps its details, and the value on record stays unless the owner changes it. If we agree with the owner, you cannot ask about that field again for 90 days unless its value changes.
You can ask once per request. Withdraw review request cancels it, and a withdrawn request cannot be sent again. Only requests an owner decided can be reviewed this way. A request AEC Integrations decided has already had our answer.
Nothing about a request or a review is public. Replies between the two companies are not part of the portal yet: each side sees the other's reason, note and reply, but there is no back-and-forth conversation.
If you are the owner and a review is requested
You see the request in Messages under Field contests, and on the integration's own page under Change requests. You can reply once, within 14 days. Our view is advice to you both. We do not change your integration.
Related
- Previous: Owning an integration.
- Next: Plans and the account label.
- The Listing Accuracy Policy sets out the contest and correction routes for everyone.
- How we research and verify listings.