Connector
OData Connector
Your system publishes an OData service? Rapidi can usually reach it through the generic OData connection.
Rapidi's generic OData connection reaches systems that publish an OData service, and reads their tables and fields from the service's metadata URL. It is a generic connection, so it cannot be guaranteed to work with every system. Business Central, Dynamics NAV and Finance and Operations have their own OData connectors instead.
- What it connects to
- Any system that publishes an OData service, in the cloud or on your own network.
- What it does not cover
- Business Central, Dynamics NAV and Finance and Operations, which have their own OData connectors.
- What you need
- The service address, its metadata URL, and a way to sign in.
What does this connector actually do?
| What it reads | The tables and fields in the service's OData metadata. You enter the metadata URL on the connection and press Read Design. |
|---|---|
| Where it points | The full path to your OData service, such as an ODataV4 endpoint on your own server or a cloud API. |
| How it signs in | No authentication, Basic with a user ID and password (and an optional account), a token, OAuth2 with Azure Active Directory, or NTLM on a local network. |
| How often it runs | On a schedule you set. The shortest interval depends on your plan, from one hour on Entry down to one minute on Unlimited. |
| Where it can run | Straight to an OData service Rapidi can reach, or through RapidiConnector for local installations and hosting you control. |
| Security | SSL is a setting on the connection, and it applies whether the address starts with http or https. |
| The caveat | It is a generic connection and cannot be guaranteed to work with every system. Ask us about yours before you plan on it. |
How do you set up an OData connection?
Setup happens in MyRapidi, on the connection itself.
- Create an OData connection in MyRapidi and give it a clear description.
- Choose the authentication type your service uses, and enter the user ID, password, domain or token it needs.
- Enter the full path to the service in Server Connect, and its metadata address in Metadata URL.
- If Rapidi can reach the service directly, delete the RapidiConnector that a new OData connection arrives with. Keep it for local installations, hosting you control, or NTLM sign-in.
- Press Test to confirm Rapidi can reach the service, then Read Design to load its tables and fields for mapping.
Which systems use this connection, and which do not?
The Rapidi documentation walks through Microsoft Graph on this connection: an app registered in Microsoft Entra ID with Graph permissions, OAuth2 sign-in, a Graph endpoint in Server Connect and the Graph metadata URL. The Microsoft ERP systems are different. They have OData connectors of their own, built for them.
Where do you go next?
Connectors
Every system Rapidi connects to
The full list, A to Z, with versions and how each one connects.
All connectors
Connector
REST Web Service
The generic connection for any system with a REST API, read from a JSON Schema or Swagger 2.0 description.
APIs and Protocols
Pricing
What Rapidi costs
Four plans, priced per subscription rather than per connector.
Plans
Your setup
Ask about your OData service
Tell us the system and what you plan to move, and we will say plainly whether this connection covers it.
Talk to a consultant
Frequently asked questions
Can Rapidi connect to any system that supports OData?
Usually, through the generic OData connection. It is a generic connection and cannot be guaranteed to work with every system, so tell us which one you run and we will check it with you first.
Is this the connector for Business Central or Finance and Operations?
No. Business Central, Dynamics NAV and Finance and Operations are reached through OData connections built specifically for them, each with its own connector page.
Which sign-in methods does the OData connection support?
No authentication, Basic with a user ID and password, a token, OAuth2 with Azure Active Directory, and NTLM on a local network. For OAuth2 with a directory other than Azure Active Directory, contact us.
Can Rapidi connect to Microsoft Graph?
Yes. The Rapidi documentation covers Microsoft Graph on the OData connection: register an app in Microsoft Entra ID with Graph permissions, sign in with OAuth2, and enter the Graph endpoint and the Graph metadata URL on the connection.
How does Rapidi learn what is in the OData service?
From its metadata. You enter the metadata URL on the connection and press Read Design, and the tables and fields become available for mapping. Repeat Read Design whenever the service's layout changes.
Does anything have to be installed on our side?
Not for an OData service Rapidi can reach directly. A new OData connection arrives with a RapidiConnector attached, and you delete it to connect directly. RapidiConnector is only needed for local installations, hosting you control, or NTLM sign-in.
What does the OData connector cost?
Nothing on its own. Rapidi is priced per subscription plan rather than per connector, so adding an OData connection does not change the licence.
Does your system speak OData?
Tell us which system you run and what has to move, and we will tell you plainly whether the OData connection covers it.