Integracionplanok API REST

Name: API REST API
Brand: Planok GCI REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey206 EndpointsREST

For Agents

Drive Planok GCI workflows for Latin American real-estate developers — owner registration, property reservations, payment channels, and post-sale notifications.

Install Jentic One Beta

Connect the API REST to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API REST, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with API REST API.

Send and resend validation codes and confirmation emails to owners

Reset owner passwords and force password changes via /guia/cambiar-password and /guia/set-force-change-pass

GET STARTED

Start building with API REST API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for the Planok GCI REST API, keeping it validated and agent-ready. Planok's GCI integration API is a 206-endpoint platform used by real-estate developers in Latin America to manage owner registration, property reservations, payment channels, and post-sale workflows for new construction projects. The surface covers owner onboarding ('guia'), online reservations, payment connectors such as Webpay, Visanet, and Iconstruye, plus WhatsApp notification hooks. Several apiKey-style schemes are in play (query keys, header keys, JWT, and a Cognito JWT) — pick the one your registered application is provisioned for.

Use Cases

Patterns agents use API REST API for, with concrete tasks.

★ Owner Onboarding for a New Project

When a new buyer purchases a unit, register them as an owner via POST /guia/registro-inicial-propietario, send a validation code, and confirm their email through /guia/confirmar-correo-propietario. The /guia endpoints model the full Planok onboarding flow used by Latin American developers, so an automation can drive sign-up end-to-end without operators copy-pasting between systems.

POST /guia/registro-inicial-propietario with the owner identifier, then trigger /guia/re-enviar-codigo-validacion if confirmation is delayed.

Online Reservation with Payment

Combine the 'Reserva En Línea' endpoints with the Webpay or Visanet channel endpoints to capture an online reservation and immediately collect payment. The flow stores the reservation, returns a Planok reservation id, and posts the payment through the right channel, removing the manual pairing step in the Planok back-office.

Create a reservation under 'Reserva En Línea', then call the Webpay channel endpoint with the reservation id and amount to collect payment.

WhatsApp Notification for Reservation Updates

Trigger WhatsApp notifications via the Whatsapp tag endpoints whenever a reservation changes state, so buyers get real-time updates on installments, document approvals, or handover dates. This avoids relying on email alone in markets where WhatsApp is the primary channel.

Send a WhatsApp notification through the configured Planok endpoint when a reservation transitions to 'paid'.

AI Agent Real-Estate Operator via Jentic

An AI agent given access to Planok through Jentic can take a buyer through registration, reservation, and payment in one conversation. Jentic handles the multi-scheme apiKey isolation and exposes each Planok operation by intent, so the agent navigates 206 endpoints without reading the docs.

Through Jentic, register the buyer via planok_register_owner, create the reservation via planok_create_reservation, and trigger the Webpay payment via the payment-channel operation.

Key Endpoints

206 endpoints — jentic publishes the only available openapi specification for the planok gci rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/guia/registro-inicial-propietario

POST

/guia/confirmar-correo-propietario

Confirm an owner's email

POST

/guia/re-enviar-codigo-validacion

Resend the owner validation code

POST

/guia/cambiar-password

Change an owner's password

GET

/guia/trae-estado-propietario

Get an owner's current state

POST

/guia/preguntas-frecuentes

Submit a frequently-asked-question request

POST

/guia/registro-inicial-propietario

POST

/guia/confirmar-correo-propietario

Confirm an owner's email

POST

/guia/re-enviar-codigo-validacion

Resend the owner validation code

POST

/guia/cambiar-password

Change an owner's password

GET

/guia/trae-estado-propietario

Get an owner's current state

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Planok exposes multiple apiKey schemes (query, header, and JWT-style). All of them are stored encrypted in the Jentic vault and bound to the right parameter location at execution time, so the agent only ever sees structured request and response data.

Intent-based discovery

Agents search Jentic by intent (for example 'register a Planok owner' or 'create an online property reservation') and Jentic returns the matching operation across the 206 endpoints with its input schema and the correct security scheme.

Time to first call

Direct integration: 5-10 days to navigate seven security schemes, owner workflows, channel-specific payments, and WhatsApp hooks. Through Jentic: under 1 hour.

FAQs

Specific to using API REST API through Jentic.

Why is there no official OpenAPI spec for the Planok GCI API?

Planok does not publish an OpenAPI specification for the GCI integration API. Jentic generates and maintains this spec so that AI agents and developers can call API REST via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Planok GCI API use?

The spec defines several apiKey-style schemes: APIKey (query parameter 'apikey'), APIKeyPublic (header 'xApiKeyPublic'), JWT (Authorization header), XAPIKey (header 'X-API-KEY'), CognitoJWT (header 'Token'), NotificacionPush (query 'codigoAplicacion'), and Planok (query 'sharedSecret'). Endpoints declare which scheme they require, so use the one your client application is provisioned for. Through Jentic, all of these credentials are held in the encrypted Jentic vault.

Can I create online property reservations through this API?

Yes. The 'Reserva En Línea' tag groups the online-reservation endpoints, which create and read reservations against project units. Combine these with the channel-specific endpoints (Webpay, Visanet, Iconstruye, Pok Pagos) to take payment alongside the reservation.

What are the rate limits for the Planok GCI API?

The OpenAPI specification does not encode explicit rate limits. Owner-onboarding and reservation endpoints are typically driven by user actions, so design around per-event calls, paginate any list endpoints, and back off on 429 responses returned by the gateway.

How do I register a property owner through Jentic?

Install with pip install jentic, then run the search-load-execute flow with the query 'register a Planok property owner'. Jentic returns the operation backed by POST /guia/registro-inicial-propietario; the agent supplies the owner identifier and any required project context.

Can the API send WhatsApp notifications?

Yes. The 'Whatsapp' tag groups endpoints that trigger WhatsApp notifications on reservation events. They are intended to keep buyers updated on installments and document state on a channel that dominates messaging in many Latin American markets.

Integracionplanok API REST

Connect the API REST to your agent

Capabilities

Start building with API REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs