Integrating 1C with Mobile Apps via REST API

We constantly face a situation: a B2B client keeps accounting in 1C and needs to "just" connect a mobile app. The typical request: "Make orders from the mobile app automatically land in 1C, and update stock levels in real time." Simplicity is deceptive — the zoo of configurations (Accounting, Trade Management, ERP, UNF, Payroll) turns a routine task into a project with hidden pitfalls. Each configuration has its own data structure, and what works in Trade Management 11 does not work in ERP 2.5. Let's dive into technical solutions and common pitfalls. Experience shows that a properly designed integration of 1C with a mobile client pays for itself within a few months. In this article, we'll cover what problems we solve, how to choose the integration method, and what to focus on during implementation. Our team has completed dozens of projects linking 1C with mobile apps on iOS and Android, including offline warehouses, courier services, and retail point-of-sale networks. With over 50 successful integrations and 8 years of expertise, we offer a detailed work plan and documentation at each stage.

What Problems We Solve

Synchronizing catalogs. A product database of 50,000 items — full export every time is unacceptable. Solution: an HTTP service with a modified_since parameter that returns only changed items. Implementation on the 1C side uses ThisObject.DateModified. Frequency: catalogs every 30-60 minutes, prices on document opening. A proper implementation saves staff time and reduces manual entry errors. Businesses using our integration save up to $20,000 annually in data entry errors.

Retrieving stock balances. A query to the accumulation register via OData: GET /odata/standard.odata/AccumulationRegister_TovarыNaSkladах/Balance?$filter=... — slow on large databases. Optimization: an HTTP service with SELECT + GROUP BY, cache in middleware with TTL 2-5 minutes.

Creating documents (orders, waybills). Transaction on the 1C side: HTTP POST → 1C creates an object, posts it, returns the number. If there is an error, a meaningful response is needed (not just 500). Agree on the error format with the 1C developer upfront.

Which Integration Method to Choose?

1C HTTP Services — a native option for modern configurations. Business logic stays inside 1C, no third-party components. Downside: requires a 1C developer, limited performance (1C is not optimized for high concurrency). OData Interface — publishes objects without code, but limited (expand one level, not all filters). Middleware (recommended) — a Node.js/Go/.NET service calls 1C via HTTP services or OData, caches, transforms, and returns concise JSON to the mobile client. This is faster and more flexible: middleware processes requests 10 times faster than direct 1C calls.

1C documentation: HTTP Services — the foundation for implementation.

How to Ensure Data Transfer Security?

1C supports Basic Auth out of the box. For production, HTTPS and a technical user with minimal rights are mandatory. OAuth 2.0 — only via an external IdP (Keycloak) with mapping in middleware. On the mobile client, credentials are stored in Android Keystore + EncryptedSharedPreferences or iOS Keychain. Never use SharedPreferences or UserDefaults. Proper authentication protects against financial loss. Our solutions are tested and conform to industry security standards.

Offline Warehouse on Android: Integration with 1C

A typical task: a mobile handheld scanner on Android in a warehouse area with poor WiFi. The operator scans barcodes, creates an inventory — data is saved locally in Room. When network appears, a batch is sent to 1C in one request. The 1C HTTP service accepts an array of items, creates an inventory document, and returns the result. On mobile: status "queued" → after confirmation "sent", local copy marked as synchronized. Delta-sync of catalogs via the modified_since parameter — only changed records. This significantly reduces infrastructure costs. Typical integration cost for a medium business ranges from $8,000 to $15,000 depending on complexity. Contact us if you need offline mode implementation.

Process of Work

1. Audit of 1C configuration — determine data structure, version, ability to publish HTTP services.
2. API design — define methods, request/response formats, authentication scheme.
3. Implement HTTP services in 1C — development and testing (usually 1-2 weeks).
4. Develop middleware (if needed) — caching, transformation, error handling.
5. Integrate with mobile client — configure REST client, handle offline mode.
6. Testing — load testing (simulate peak requests), functional, edge cases.
7. Deploy — publish on web server, configure HTTPS, TestFlight/Google Play.

Our certified 1C specialists with 8+ years of experience guarantee integration stability and provide SLAs.

What's Included in the Work

• API documentation (OpenAPI/Swagger specification).
• Code for 1C HTTP services (or middleware).
• Deployment and access setup instructions.
• Training for your developers (1-2 hours online).
• Technical support for 30 days after launch.

Timelines and Cost

Audit of 1C configuration and API design — 3-5 days. Basic integration (reading catalogs and stock levels, creating documents) via HTTP services — 3-6 weeks. Full offline support, delta-sync, error handling — plus 2-3 weeks. Cost is calculated individually, depends on the 1C configuration and customization scope. Typical integration cost for a medium business ranges from $8,000 to $15,000. Get a detailed plan — contact us.

Our experience shows: a properly designed integration pays for itself. Contact us to evaluate your project.

Trusted by 50+ companies. Guaranteed results.

How to Start Integrating API into a Mobile App?

The request goes out, the response doesn't come, timeout — 30 seconds. The user stares at the spinner. No network — mobile card in the subway. Or the network is there, but the server returns 200 with an HTML error page instead of JSON — and the app crashes on JSONDecoder.decode(). We see such cases on every second project. So integrating API into a mobile app is not just calling an endpoint, but designing a reliable network layer: error handling, caching, offline mode, certificate pinning. Order an audit of your current network layer — we will evaluate the project in 1 day. Our team guarantees a thorough analysis and provides a detailed roadmap.

Standard libraries like URLSession and OkHttp provide basic HTTP clients, but for production you need retries with exponential backoff, status code validation, typed deserialization, and network state monitoring. Without this, the app loses data and users. We have been doing mobile development for 5 years and implemented more than 30 projects with API integration on iOS, Android, and Flutter — from startups to enterprise solutions.

How to Choose a Protocol for API Integration?

REST remains the standard for most projects. But when a profile screen needs 5 fields out of 40, GraphQL eliminates over-fetching and reduces traffic by 30–60%. gRPC is justified for thousands of requests per minute (trading, IoT) — binary serialization is 3–5 times faster than JSON. WebSocket is the only choice for real-time without polling (messages, notifications).

Practical example: For a fintech app, we replaced REST (40 fields) with GraphQL — response size dropped from 12 KB to 2.5 KB, screen render time decreased by 70%. Traffic savings were significant. Our certified iOS and Android developers have deep experience with all these protocols — you can rely on proven solutions.

How to Ensure Reliable Connection and Offline-First?

Users lose network in the subway, elevator, tunnel. A mobile app must work without internet — at least in read-only mode. We implement the offline-first pattern:

1. On screen open, first show data from the local cache (Core Data / Room).
2. Simultaneously perform a network request, update UI after response.
3. If network is unavailable — show cached data and a 'no connection' label.
4. When network is restored, automatically synchronize changes.

For HTTP response caching we use URLCache (iOS) and OkHttp Cache (Android) with Cache-Control support. For structured data — SwiftData / Room. NWPathMonitor / ConnectivityManager.NetworkCallback monitor network state and trigger updates.

REST and Client Library Selection

Alamofire (iOS) — de facto standard for Swift projects. On top of URLSession it adds request chaining, response validation, automatic retry, certificate pinning via ServerTrustManager. AF.request() with .validate() returns an error for any status code outside 200–299. Without .validate(), Alamofire considers 404 and 500 as successful responses. With Swift Concurrency — async version via serializingDecodable.

Retrofit (Android) — annotation-based HTTP client on top of OkHttp. An interface with annotations compiles into implementation. @GET, @POST, @Path, @Query, @Body — declarative API description. OkHttp under the hood: connection pooling, transparent gzip, HTTP/2 multiplex. HttpLoggingInterceptor — logging in debug builds. Authenticator — automatic token refresh on 401.

Ktor (KMM/Flutter) — multiplatform HTTP client. On iOS it works via Darwin engine (URLSession), on Android — via OkHttp. Single code for both platforms with KMM architecture.

GraphQL: When REST Falls Short

REST returns a fixed structure. A profile screen needs name, avatar, email — the server sends 40 fields. Over-fetching. GraphQL solves this: the client requests exactly the needed fields. This is critical for mobile where traffic and parsing time are real constraints. Apollo iOS and Apollo Kotlin generate typed classes from schema: schema.graphql + query files → strict types at compile time. Subscriptions via WebSocket — real-time without polling. Limitation: GraphQL is harder to cache at the HTTP level. Apollo uses a normalized in-memory cache InMemoryNormalizedCache — requests with overlapping data update the cache without duplication.

WebSocket: Real-Time Without Extra Traffic

Polling (setInterval every 5 seconds) — battery and traffic waste. WebSocket is a persistent bidirectional connection. iOS: URLSessionWebSocketTask (native, iOS 13+). Android: OkHttp WebSocket. Mandatory reconnect handling: on onFailure — exponential backoff (1s → 2s → 4s → 8s → max 60s). Socket.IO is an overlay with automatic reconnect, but for new projects native WebSocket is preferable (fewer dependencies).

gRPC: For High-Load Services

gRPC with protobuf — binary serialization: smaller size, faster parsing. grpc-swift for iOS, grpc-kotlin for Android. The protobuf schema compiles to typed classes. Streaming (server-side, client-side, bidirectional) is a native feature. Application threshold: high request frequency (trading, IoT) or critical latency. For regular CRUD, REST is simpler to debug and monitor.

Certificate Pinning and Security

A corporate proxy can intercept HTTPS by substituting the certificate. Certificate pinning prevents this: the app accepts only a specific certificate or public key. Alamofire: ServerTrustManager with PinnedCertificatesTrustEvaluator. OkHttp: CertificatePinner with SHA-256 hash. Apple's App Transport Security documentation recommends pinning certificates for sensitive data. Operational complexity: on certificate rotation, older app versions stop working. Solution — pinning to the CA public key or support multiple pins with a grace period.

What Is Included in the Work

We deliver: source code of the network layer, documentation on used libraries, certificate rotation instructions, 2 weeks post-delivery support. Our experience guarantees that the solution will be stable and maintainable.

Timeline and Cost

Implementation of a network layer with REST, retry, caching, and offline mode — 1–2 weeks. Adding GraphQL or WebSocket — another 1–2 weeks. gRPC — 2–3 weeks, including code generation. The cost is calculated individually after analyzing the API and offline behavior requirements. We will evaluate the project in 1 day — contact us for a consultation. Get a reliable API integration with guaranteed quality.