GoReportly
GoReportly is a REST API that turns JSON data into branded PDF reports. Developers define a Razor template once, post their data, and receive a styled document in seconds, with no PDF library to maintain.
What is GoReportly?
GoReportly is an online service that turns JSON data into finished PDF documents through a REST API. Its homepage states the proposition plainly: automated PDF reporting using JSON, define your template once and call the API whenever you need a document.
The workflow has three steps. You design a report template using Razor (CSHTML) syntax, upload it under a unique name, then post your data to the API and receive a styled PDF in seconds. Templates behave like familiar HTML pages enriched with server-side expressions: you read values with @Model.PropertyName, iterate over collections with @foreach and branch with @if. The model type declaration normally found at the top of a Razor file must be omitted. Styling is done with inline CSS or an embedded CSS block inside the template, and images can be pulled from public URLs or embedded as Base64 data URIs.
Two endpoints do the work. POST /api/report renders one document from a single data object. POST /api/reports repeats the same template over an array of objects, each producing a page, with a hard ceiling of twenty-five items per call. Both take a templateName and a templateData field, both require an API key in the Authorization header, and both answer with a 200 response whose body is an application/pdf file. The vendor publishes an OpenAPI 3.0.4 specification and a Swagger explorer, so the whole contract can be inspected and tried before any integration work begins.
A web dashboard handles the account, which is opened with nothing more than an email address and a password. The homepage carries three worked examples, an HR employee list, a telecom invoice and a batch of invoices, each showing the template, the input JSON and the generated PDF side by side.
The main operational argument is that nothing has to be installed or maintained on your side: no PDF library, no rendering engine, no fonts to manage. GoReportly claims no artificial intelligence capability of any kind: it is a template rendering engine, not a content generator. It is also a very small operation, five public pages, one price and one support email address, running on a domain registered in September 2025.
What it does
- Convert a JSON payload into a styled PDF through a single API call
- Generate a multi-page PDF from up to 25 data objects in one batch request
- Design reusable document templates in Razor (CSHTML) syntax
- Loop over collections and apply conditional logic inside a template
- Style documents with inline CSS or an embedded CSS block
- Embed images from public URLs or Base64 data URIs
- Test every endpoint from the online Swagger explorer before integrating
When to use GoReportly / When not to
A quick filter to help you decide if GoReportly is the right fit.
When to use GoReportly
- Back-end and full-stack developers who need to produce invoices, statements or reports from an existing application
- Small technical teams staying under 1,000 documents and 20 templates a month
- .NET developers already fluent in Razor and CSHTML syntax
- Startup founders and freelance developers who want PDF output without maintaining a rendering engine
- Data and BI engineers turning JSON pipelines into batch documents, up to 25 records per call
When not to use GoReportly
- Organisations whose purchasing goes through a legal review, since no terms, privacy policy or DPA are published
- Teams with strict GDPR obligations, as the site never mentions the regulation, its subprocessors or its hosting locations
- Non-technical users, who would still need a developer to write a Razor template and sign the HTTP calls
- High-volume operations beyond 1,000 reports a month, which require a quote negotiated by email
- Anyone looking for interactive dashboards or charts rather than fixed PDF documents
How to use GoReportly
A typical end-to-end flow, from setup to results.
- Create an account on the signup page with an email address and a password; no credit card is required
- Retrieve your API key from the web dashboard
- Write your document as an HTML template enriched with Razor expressions, omitting the model type declaration
- Style it with inline CSS and add images as public URLs or Base64 data URIs
- Upload the template under a unique name, which becomes your templateName
- Try the call from the Swagger explorer to check your payload before writing any code
- Send a POST request to /api/report with your API key in the Authorization header and a JSON content type
- Pass templateName and templateData in the request body
- For a batch, call /api/reports instead and pass templateData as an array of up to 25 objects
- Collect the 200 response, whose body is the generated PDF file, and serve or archive it on your side
Pros & Cons
Pros
- Deliberately narrow scope: one job, done end to end, with no configuration sprawl
- Published OpenAPI specification and live Swagger explorer, so the integration can be verified before paying
- Nothing to install or maintain: no PDF library and no rendering engine on your infrastructure
- Flat, publicly displayed pricing with no hidden tiers
- Ten-day free trial that asks for no credit card
- Native batch generation, up to 25 documents in a single call
- Complete worked examples, template, input JSON and resulting PDF, downloadable from the homepage
Cons
- No terms and conditions, no privacy policy and no legal notice are published anywhere on the site
- No company name, postal address or named officer, even after off-site searching
- No GDPR statement, no DPA, no subprocessor list and no announced hosting country
- Hard quotas of 1,000 reports and 20 templates per month, with no intermediate tier published
- Razor and CSHTML impose a learning curve on anyone outside the .NET ecosystem
- No SDK, no named third-party integration and no no-code connector
- A single support channel, one email address, with no service commitment or status page
Pricing & Plans
There is no permanent free plan. Access is subscription-based and the lowest entry point is USD 9.99 per month, with an annual subscription offered at USD 99.99 per year for the same allowance. Both formulas include 1,000 reports per month, 20 custom templates, batch generation of up to 25 documents at a time, error support and legacy template conversion. A ten-day free trial is available and requires no credit card. High-volume or specific use cases are quoted individually on request by email. No refund, cancellation or payment-method information is published.
- 1
- 000 reports per month
- 20 custom templates
- batch reporting up to 25 simultaneous
- error support included
- legacy template conversion
- same allowance as the monthly formula
- namely 1
- 000 reports per month
- 20 custom templates
- batch reporting up to 25 simultaneous
- error support included
- legacy template conversion
- Custom plan
- price on request by email
- for high-volume or specific use cases
- Free trial
- 10 days
- no credit card required
Data, GDPR & hosting
A consolidated view of how GoReportly handles your data.
GDPR overview
There is no GDPR implementation to report. Searching the whole collected archive, six pages in text and raw HTML, returns not a single occurrence of GDPR, DPA, data processing agreement, controller, processor or subprocessor. No privacy policy, no terms and conditions and no legal notice exist: the twelve usual legal URLs all return 404. No Article 27 representative is designated, no data protection officer is named, and no GDPR contact address is published. The only address on the site, mysupport@goreportly.com, is presented as commercial and technical support. Signing up requires no consent and displays no legal checkbox. The nearest statement is one homepage sentence saying that requests and completed reports are never stored. For a European buyer, that leaves no identifiable contractual counterparty and no documented basis for processing.
Who owns the data?
No terms and conditions and no privacy policy are published on the site, so data ownership is not contractually settled anywhere. Nothing states who owns the JSON you send, the templates you upload or the PDF files the service returns, and no licence, assignment or reuse clause appears on any page. The only related statement sits on the homepage, where the vendor writes that requests and completed reports are never stored. That claim addresses retention, not ownership, and it is repeated in no binding document. In practice, buyers get no written commitment about their data and no identified counterparty to hold to one.
Reuse rights
Nothing restricts what you do with the output. There are no terms and conditions, so the service imposes no licence, no attribution requirement and no limit on reusing the PDF files it returns: the documents are built from your own data and your own template, and you may distribute, sell or archive them freely. On the vendor's side, the stated use of your data is narrow. The JSON you post feeds the template and produces the PDF that comes back, and the homepage adds that requests and completed reports are never stored. Account creation asks only for an email address and a password, calls are authenticated with an API key, and no analytics, cookies, tracking or third-party sharing is mentioned anywhere. All of this rests on a single homepage sentence rather than on a contract.
Data retention & training
Hosting summary
The vendor publishes nothing at all about where data are hosted: no country, no region, no cloud provider, no jurisdiction and no transfer clause. There is no privacy policy, no terms and no trust page in which such information could appear, and no subprocessor is disclosed. The only adjacent statement is the homepage claim that requests and completed reports are never stored, which speaks to retention rather than to location. A network observation carried out on 6 September 2026, an observation and not a vendor declaration, shows the domain resolving to 13.62.82.190, an address geolocated in Stockholm, Sweden, on Amazon Web Services (AS16509), without anycast. That suggests European infrastructure, but it is inferred from DNS and IP geolocation alone, it can change without notice, and it carries no contractual weight. A buyer who needs a documented hosting jurisdiction, for a data protection impact assessment or a supplier questionnaire, will find nothing usable here and should ask the vendor directly.
Things to keep in mind
Risks and trade-offs to weigh before adopting GoReportly.
- No contract of any kind: with no terms, privacy policy or legal notice, you have no written recourse and no identified counterparty if something goes wrong
- The operator is anonymous, with no company name, address or named officer, which makes any dispute, audit or supplier assessment impossible
- Business data travel in the request body of every call, and the only assurance about them is a single sentence on a marketing page
- The templates you upload stay on the service, and no document says how long they are kept or how to delete them
- The domain expires in September 2026 and the service publishes no status page or service commitment, so a quiet shutdown would take your document pipeline with it
- Convenience breeds dependence: once invoices or statements are generated remotely, an outage or a price change hits a process you no longer control in-house
- The resolved server sits in Sweden on Amazon Web Services while nothing about hosting is declared, so any assumption you make about jurisdiction is your own, not the vendor's
Setup & Integrations
Technical difficulty
Moderate, and developer-only. There is nothing to install and no infrastructure to provision, but you must write an HTML template in Razor syntax and issue authenticated HTTP POST requests, so a non-technical user cannot get started alone. Signing up takes two fields and no card, the whole documentation fits on one page with request and response examples, and the Swagger explorer lets you test before integrating. The vendor identifies template writing as the main friction point and offers free help with it by email. There is no visual template designer: everything is done in code.
Deployment
Behind GoReportly
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
What does GoReportly actually do?
How are the templates written?
Which endpoints does the API expose, and how do I authenticate?
How many documents can one batch call produce?
What does it cost, and is there a free plan?
Are my data kept by the service?
Does GoReportly publish terms of service or a privacy policy?
Can I test the API before committing?
What if I need more than 1,000 reports a month?
Is help available if a template does not work?
Should you pick GoReportly?
GoReportly does one thing and documents it well. A Razor template, two endpoints and an API key are the whole product, and the published OpenAPI specification plus the live Swagger explorer let a developer confirm the integration works before spending anything. Pricing is flat and visible, USD 9.99 a month or USD 99.99 a year for a thousand documents and twenty templates, the trial asks for no card, and the vendor even offers free help writing templates. For a team that needs invoices or statements out of an existing application and does not want to maintain a rendering engine, that is a reasonable and cheap proposition.
The reservations are institutional rather than technical. The site publishes no terms of service, no privacy policy, no legal notice, no company name and no postal address. There is no GDPR mention anywhere, no subprocessor list, no data processing agreement and no declared hosting jurisdiction. The single reassurance on offer is one homepage sentence stating that requests and completed reports are never stored, a claim no document backs. The quotas are modest, the batch ceiling is twenty-five, support is a single email address, and there is no status page or service commitment. The domain itself was only registered in September 2025.
The arbitration is therefore straightforward. Where PDF output is a secondary need, the data are not sensitive and the budget is small, GoReportly is an efficient shortcut. Where the purchase passes through a legal or privacy review, or where the documents carry personal or regulated data, the absence of any identifiable contractual counterparty makes it unsuitable, however well the API itself is put together. Treat the technical quality and the documentary opacity as two separate judgements.
- Choosing a selection results in a full page refresh.
- Opens in a new window.