Zig
Zig
Egyptian eReceipt OAuth2 Client Credentials
See more Egypt eReceipt Examples
Get an OAuth2 access token for the Egyptian eReceipt REST API using client credentials (no interactivity with a web browser required).Chilkat Zig Downloads
const std = @import("std");
const chilkat = @import("chilkat");
pub fn main(init: std.process.Init) !void {
const alloc = init.arena.allocator();
// This example assumes the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.
const http = try chilkat.Http.init();
defer http.deinit();
// Note: Any provider of a REST API, such as the Egyptian government in this case, can make life
// much easier for developers by providing one or more of the following in the API documentation:
//
// 1) A sample CURL statement for each API call.
// 2) A Postman collection, or Swagger/OpenAPI specification file.
// 3) A sample of a raw HTTP request and response for each API call.
//
// The sample CURL statements or raw HTTP request/responses do not need to comprehensively show all
// possible options. Providing a sample allows one to quickly make a successful API call.
// It also allows for code generation directly from the CURL, Postman collection, or raw request/response,
// and it tends to answer all questions about the format/structure of a request that, suprisingly,
// remain ambiguous or not obvious in other forms of documentation.
const req = try chilkat.HttpRequest.init();
defer req.deinit();
req.addParam("grant_type", "client_credentials");
// Use your actual client ID and client secret...
req.addParam("client_id", "d0394a9f-0607-40de-a978-2d3eb8375b04");
req.addParam("client_secret", "6d62315e-d65a-4e41-9112-4195ea834edf");
req.addHeader("posserial", "1234567899");
req.addHeader("pososversion", "os");
req.addHeader("posmodelframework", "1");
req.addHeader("presharedkey", "03ac674216f3e1...");
// When writing this example, the documentation at https://sdk.invoicing.eta.gov.eg/ereceiptapi/01-authenticate-pos/
// shows us the HTTP verb and path (POST /connect/token), however,
// we don't see the actual domain where the request is to be sent.
// What are the endpoints???
// It took some searching, but we found some endpoints here: https://sdk.invoicing.eta.gov.eg/faq/
// It's not immediately apparent which endpoint is to be used with a given API call.
// Why not just include the endpoint in the documentation for each REST API call?
// Endpoints are literally the #1 thing that needs to be known.
// They can't just be buried in a FAQ. They should be up-front and obvious.
//
// So.. we're guessing the endpoint is likely "https://invoicing.eta.gov.eg/connect/token"
req.setHttpVerb("POST");
req.setContentType("application/x-www-form-urlencoded");
const resp = try chilkat.HttpResponse.init();
defer resp.deinit();
http.httpReq("https://invoicing.eta.gov.eg/connect/token", req, resp) catch {
std.debug.print("{s}\n", .{try http.getLastErrorText(alloc)});
return;
};
const sb_response_body = try chilkat.StringBuilder.init();
defer sb_response_body.deinit();
resp.getBodySb(sb_response_body) catch {};
const j_resp = try chilkat.JsonObject.init();
defer j_resp.deinit();
j_resp.loadSb(sb_response_body) catch {};
j_resp.setEmitCompact(false);
std.debug.print("Response Body:\n", .{});
std.debug.print("{s}\n", .{try j_resp.emit(alloc)});
const resp_status_code = resp.getStatusCode();
std.debug.print("Response Status Code = {d}\n", .{resp_status_code});
if (resp_status_code >= 400) {
std.debug.print("Response Header:\n", .{});
std.debug.print("{s}\n", .{try resp.getHeader(alloc)});
std.debug.print("Failed.\n", .{});
return;
}
// If successful, the OAuth2 access token JSON looks like this:
// {
// "token_type": "Bearer",
// "access_token": "eyJraW......R2sbqrY",
// "expires_in": "3600",
// "scope": "..."
// }
_ = try j_resp.stringOf(alloc, "token_type");
_ = try j_resp.stringOf(alloc, "access_token");
_ = try j_resp.stringOf(alloc, "expires_in");
_ = try j_resp.stringOf(alloc, "scope");
}