Skip to main content
This walkthrough takes a prospective member through the adhesion (membership application) flow: create the application, attach the ID document and the signed form, submit it for review, and let HR move it to approval. It chains the Adhesion, Identity and User resources. Who is this for: integrations that surface Orgo’s adhesion flow inside a third-party site, or admin tools that drive applicants through the funnel on their behalf.
Everything here runs on the tenant host, for example acme.orgo.space. The examples use an Api-Token created by a chapter HR manager, who may act for the applicant. An applicant signed in as themselves can run steps 2 to 6 against their own application.

What you’ll end up with

Statuses are lowercase strings and transitions are explicit: Orgo never advances an application on its own.

Step 0: Make sure the applicant is a user

An application belongs to an existing User. Either the applicant registers on your site with POST /api/v1/users (the public registration endpoint, with an anti-spam honeypot and timing check), or HR creates the account with POST /api/v1/member-register-by-admin:
The new user is placed in the center you name (or in the HR manager’s own center) and gets a welcome email with a login link. Keep the returned id; the rest of the flow uses it as userId.

Step 1: Create the draft adhesion

userId is optional for an applicant creating their own application and is how HR creates one on someone’s behalf. A user can have only one application in progress: creating a second returns 400 This user already has an adhesion in progress. A new one is allowed once the previous one is rejected, canceled or marked duplicated.
Keep the adhesion id (33 here). hasUploadedDocument becomes true when the signed form is attached.

Step 2: Upload the ID document

Identity verification is on by default; a tenant can switch it off in its adhesion settings, in which case you can skip this step and the 400 ID document is missing checks below do not apply. The upload is a signed upload, not a multipart request to this endpoint. First ask for a signed upload with type=identity, send the file to the address it returns, then register it:
The ID must be an image; anything else answers 400 The image you are trying to upload does not have a recognizable image format. The call creates the applicant’s Identity record and starts text recognition (OCR). Recognition runs before the response returns, and its results appear on GET /api/v1/identity/{id}. If recognition fails, the upload still succeeds and HR can correct the fields. Uploading again replaces the previous document and its extracted data.

Step 3: Save the form data

The payload carries the personal and professional fields of the application form (address fields, townCurrent, profile links, profession fields, and the ID serial and number). Saving is only allowed while the status is new, and it needs the ID document from step 2 to exist (otherwise 400 ID document is missing, please upload it first.).
Saving the form data discards any signed form already uploaded. Always save the data first and upload the signed form afterwards, as in this order.

Step 4: Upload the signed form

Download the pre-filled PDF with GET /api/v1/adhesion/33/pdf, have it signed, and register the signed file the same way as the ID: a signed upload with type=adhesion, then:
oldMedias lists the ids of earlier signed files to remove; send [] for the first upload. The adhesion now shows hasUploadedDocument: true.

Step 5: Submit for HR review

This moves the status from new to pending and stamps sentDate. A missing document answers 400 (Signed document is missing or ID document is missing), not 409. When the applicant submits their own application, the responsible HR admin is emailed; when HR submits on their behalf, no email is sent. After this the applicant cannot edit the application.

Step 6: HR reviews and decides

HR records interview notes, then moves the status:
A tenant can switch the review steps off, or make them flexible (statuses stay available but their preconditions are dropped). A refused transition answers 400 with the reason, for example Interview and background conclusions must be written first or Identity is not present or not validated. Interview notes cannot be edited once the status is rejected or success. After success the user is a full member (isFullMember: true). The membership fee is handled separately, through the fee and payment flow, see Process payments.

Common gotchas

The email goes to the responsible HR admin of the applicant’s center, and only when the applicant submits their own application. Check that at least one administrator holds HR rights for that center (see Assigning permissions). If HR submitted on the applicant’s behalf, nobody is emailed by design.
Recognition fills the Identity record, not the application form. The applicant’s submitted fields stay as they are, and HR sees both side by side. Correct the identity with PATCH /api/v1/identity/{id}/update-data before validating it.
No. For minors, use the family-member flow: POST /api/v1/register-child against a parent’s authenticated session. It skips the ID upload and the parental application, and the child is linked to the parent’s family.
Yes, for an organization-wide HR manager. Register the account with POST /api/v1/member-register-by-admin and assign the member role with POST /api/v1/user_roles, or send rawUserRoles and userType with the registration. You skip the application altogether, so there is no audit trail of an application.

What to do next