API, Webhooks and MCP: connect Dexyd to team tools

When a team organizes a competition, a challenge or a call for projects, it almost never works with just one tool.

It can use a CRM, a reporting tool, a collaborative space, an internal dashboard, a messaging tool, a database, a support system, an analysis platform or an AI assistant.

If Dexyd remains isolated, teams must copy data, export files manually, track submissions in multiple locations, and repeat the same actions.

The API, webhooks and MCP help prevent this.

They transform Dexyd into a platform that can be connected to professional workflows.

1. Why connect Dexyd to other tools?

A contest is not limited to a public page.

Behind a competition, there may be:

• registrations;
• submissions;
• votes;
• juries;
• talent profiles;
• Expo projects;
• reports;
• marketplace requests;
• notifications;
• internal decisions.

For a small team, the Dexyd interface may be sufficient. For a large team, an agency, a school or a company, it often becomes useful to connect this data to other tools.

For example:

• send new submissions to an internal tool;
• synchronize participants with a CRM;
• track votes in a dashboard;
• trigger a notification when a project is finalist;
• export the results to a reporting tool;
• link selected talents to a collaborative process;
• connect Dexyd to internal AI assistants.

This is where integrations become important.

2. The Dexyd API: access essential data and actionsAn API allows a team or developer to connect Dexyd to other systems.

Depending on the plan and the permissions available, the API can allow you to work with:

• competitions;
• submissions;
• the participants;
• Expo projects;
• the results;
• exports;
• talent profiles;
• marketplace requests;
• some reports.

The goal is not just to read data. The objective is to allow teams to build workflows adapted to their organization.

An agency can connect Dexyd to its customer tracking table. A school can centralize student projects. A company can integrate the results of a challenge into its internal system. An incubator can track its cohorts and finalists.

The API gives more flexibility to advanced uses.

3. Webhooks: receive events at the right time

An API often allows you to request information.

A webhook allows Dexyd to automatically send information when an event occurs.

For example:

• a new submission is received;
• a competition goes to the voting phase;
• a vote is recorded;
• a participant joins a team;
• a project becomes a finalist;
• a provisional result is published;
• a marketplace request is created;
• a report is available.

Webhooks avoid manually checking the status of the platform.

They allow you to trigger actions in other tools:

• send an alert to a team;
• update a dashboard;
• create a task;
• notify a jury;
• feed a reporting system;
• synchronize data.

For teams running multiple contests, webhooks provide a lot of continuity.## 4. MCP: connect Dexyd to AI assistants and advanced workflows

MCP allows for further integration with AI assistants and systems capable of interacting with external tools.

In Dexyd logic, MCP can allow advanced environments to better understand the context of the platform and interact with certain elements according to the planned authorizations.

This is particularly useful for large accounts, technical teams, organizations that already use AI agents or complex internal workflows.

With MCP, Dexyd can become a source of action and context for broader assistants.

For example, a team may want an internal assistant to help:

• find active competitions;
• read submissions;
• compare results;
• prepare a report;
• suggest talents to contact;
• follow Expo projects;
• retrieve selection data;
• coordinate actions between several tools.

MCP is a strategic capability. It must be supervised, secure and reserved for advanced uses.

5. Why MCP should not be in every plan

MCP, advanced API, white label, SSO, SLA and business integrations are not just convenience options.

These are abilities that relate to:

• security;
• the data;
• permissions;
• internal workflows;
• liability;
• the technical load;
• customer support.

It therefore makes sense to reserve these functions for the most advanced plans, notably Enterprise.

This protects the platform and allows us to better support customers who have real integration needs.A small team can use Dexyd directly from the interface. A Scale framework can have a limited API and limited webhooks. A large account can go through Enterprise for MCP, advanced API, business integrations and enhanced security.

This separation makes the offer clearer.

6. Limited API, advanced API: what's the difference?

Not all integrations have the same level of complexity.

A limited API may be enough to:

• read competitions;
• retrieve submissions;
• export results;
• follow some events;
• connect a simple dashboard;
• receive basic webhooks.

An advanced API can go further:

• fine permissions;
• high volumes;
• multi-organization;
• business integrations;
• complex automations;
• reinforced security;
• synchronization with internal systems;
• personalized reporting;
• specific workflows.

This is why it is useful to separate the levels.

The goal is not to block users. The goal is to give each team the right level of access, at the right level of responsibility.

7. Security and permissions

When a platform is connected to external tools, security becomes essential.

You must be able to control:

• who can create an API key;
• what data is accessible;
• what actions are authorized;
• which events are sent;
• which webhooks are active;
• which external systems receive the data;
• how access is revoked;
• how actions are logged.

For large accounts, these questions are even more important.

A poorly controlled integration can expose sensitive data, disrupt a competition, or create errors in workflows.This is why Dexyd must treat integrations as a business capability, not just a box to check.

8. Examples of professional uses

An agency can connect Dexyd to its campaign monitoring tool to show its clients the evolution of participations.

A school can automatically export student projects to an educational tracking table.

An incubator can monitor the finalist teams and prepare the next stages of support.

A brand can link a sponsored challenge to its CRM to identify the most engaged talents or communities.

A company can use webhooks to notify its internal juries when a new important submission arrives.

A large account can connect Dexyd to its internal AI assistants using MCP, in a secure and validated framework.

These uses show that integrations are not just for developers. They serve to better circulate information.

9. The role of Oria in integrations

Oria can also help make better use of integrations.

It can explain what a webhook means, help understand the data in a report, prepare a summary or direct the user to the right export.

In advanced contexts, Oria can help teams formulate their needs:

• what data to track;
• what events to monitor;
• what reports to generate;
• which actions to automate;
• what limits to respect.

Oria does not replace the technical team. It helps make workflows more understandable.

10. Why these tools strengthen Dexyd

A competition platform can work alone.

But a professional platform must be able to integrate.APIs, webhooks and MCP allow Dexyd to be part of the real uses of teams: reporting, CRM, AI, internal tools, customer monitoring, educational programs, marketing campaigns and innovation workflows.

This gives Dexyd greater value for organizations that don't just want to run a competition, but integrate the results into the way they work.

Dexyd then becomes more than a publication space. It becomes a connected brick in a larger system.

Conclusion

Competitions, votes, juries, talent profiles and Expo projects produce useful data.

The API provides access to this data. Webhooks allow you to receive events at the right time. MCP connects Dexyd to advanced AI assistants and workflows.

These tools must be offered seriously, according to the right levels of plan, security and support.

For simple teams, the Dexyd interface is sufficient. For advanced teams, integrations open up new possibilities. For large accounts, MCP, advanced API and reinforced security become strategic levers.

Good integration does not replace the product. It extends its value into the tools that teams already use.