Is there a API endpoint to create a new merchant? Can't find it in https://docs.clover.com/clover-platform/reference
Upon creation of a merchant, what's the user flow? Do they receive an email to validate my permissions?
Is there a API endpoint to create a new merchant? Can't find it in https://docs.clover.com/clover-platform/reference
Upon creation of a merchant, what's the user flow? Do they receive an email to validate my permissions?
You can't create a merchant through REST APIs. Merchants are added to our system through an onboarding process.
Maybe you can give more details about what you are trying to do.
A merchant that uses clover wants to register with my app. They go on my website, fill a form, give me their consent and information. When they confirm, I'd like to send a request to one of your endpoints, receive the mId in the response, and from now one have that merchant enrolled in my app.
It seems like you are trying to solve a different problem than how to create a merchant. You want to offer an interface on your website that allows an existing Clover merchant to install your app to their existing Clover merchant account, is that correct? I think you should create a new community question for this.
Per your original question, Jeff is correct, you cannot create a merchant via the REST API.
"Yes, just REST calls on their behalf. Is that possible?"
It is possible but you need to have a Clover webapp (https://docs.clover.com/clover-platform/docs/clover-development-basics-web-app) - otherwise anyone would be able to get merchant data without their approval. Once you have an approved webapp the merchant needs to grant it the authority to make calls on their behalf which is done by following our OAUTH2 flow - https://docs.clover.com/clover-platform/docs/using-oauth-20.
Thanks David. What if my "app" is actually a REST api itself, that lives in my cloud space. I should still be able to GET my customer's (the merchant) data, shouldn't I?
Yes, the web-app is largely a mechanism to allow you to obtain a token. When your merchant logs in and wants to install your Clover web-app you will guide them through the OAUTH2 flow, obtain a token for them and securely store it (good for one year). You will then be able to use that token to make api calls.
I see, thanks. What's the review process you have for the "apps"? And what the requirements? I read the link you sent, but what about our (private) source code? The page speaks about bug-checks: do you run automated tests, or what else?
3 People are following this question.