rent a number
rent a number from the inventory. the first month’s rent is taken from the wallet up front, then the KYC goes to the carrier; the rental then moves through kyc_submitted → kyc_accepted → purchasing → active (poll GET /v1/phone-numbers/{number_id}, its timeline says where it is). a short wallet parks the rental in funding until auto-pay tops it up.
with documents — multipart/form-data: a data field holding the JSON below and the document files in documents order (pdf, jpeg or png, 5 MB each). KYC already verified (see verifiedKyc on the requirements) — a plain JSON body with just requestedNumber.
Authorizations
your rumik api key, e.g. rk_live_.... create one in the rumik dashboard.
Body
the rental payload — the JSON body, or the data field of the multipart form.
the number to rent, as returned by the search (number, bare digits, or e164).
"918046800123"
the filters the number was found with (pattern, city), so a substitute can be picked from the same search if the number is taken meanwhile.
the business renting the number: name (required, the legal name), email, address_line1, address_line2, city, state, postal_code, country, registration_number. required when documents are sent.
one entry per required document type from the requirements: documentTypeId and its dataFields. the files go in the multipart files field, in this order.
Response
created.
a number rented through rumik, with its lifecycle.
the rental's id.
funding → kyc_submitted → kyc_accepted → purchasing → awaiting_funds → active; kyc_rejected, past_due, releasing, released, failed.
the wallet's currency (INR).
the rental's progress, step by step: key, label, state (done | active | pending | failed), at, detail.
the raw event log.
what was asked for.
the number owned (bare digits), once purchased.
the same in E.164 — what fromNumber on POST /v1/calls takes.
the monthly rent in the wallet's currency, in nanos (billionths).
one-off setup fee, nanos.
inbound per-minute carrier rate, nanos.
outbound per-minute carrier rate, nanos, billed per outboundUnitSeconds.
the outbound billing pulse (30 s for India).
the first charge collected before the KYC went out.
when the number was purchased.
when the next month's rent is due.
why it was released (user, non_payment, …).
the last carrier or billing error, if any.
the agent connected to the number, or null.
that agent's name.
the KYC application: status, rejectionReason, attempts, history.