Sahitya1 Documentation Center
Searchable guidance for admins, dashboard users, and developer API buyers.
Client login required
Please log in with your assigned Sahitya1 client account to access literature records and filters.
Sahitya1 Membership
Sign in to access your tool membership, activate the free plan, and manage future subscriptions for the literature dashboard.
Free for now
Payment, paid subscriptions, and full checkout for dashboard users will be connected after the rest of the platform is complete.
Sahitya1 Developer API
Sign in to activate developer API access, generate keys, and manage your future API plan separately from dashboard membership.
Developer API track
This portal is separate from end-user dashboard membership. Paid API products and request tiers can be attached later without affecting tool subscriptions.
Sahitya1 Documentation Center
Searchable guidance for admins, dashboard users, and developer API buyers.
Docs + Q&A
Dashboard: [sahitya1_dashboard]
Membership: [sahitya1_membership]
API Portal: [sahitya1_api_portal]
Docs: [sahitya1_docs]
Guides
4 sections
All
Platform Overview
Understand how Sahitya1 is structured across dashboard usage, admin management, and developer API access.
What Sahitya1 does
Sahitya1 stores literature records in a reusable database, lets admins organize that data by client, drug, and weekly batch, and gives assigned users a filtered dashboard to search and export their literature.
Three product layers
The plugin now has three separate layers: the literature database, the user-facing membership for dashboard access, and the developer-facing API product for external integrations.
Recommended page shortcodes
Use [sahitya1_dashboard] for the literature dashboard, [sahitya1_membership] for user membership access, [sahitya1_api_portal] for developer API access, and [sahitya1_docs] for the full documentation page.
Admin
Admin Guide
Step-by-step guidance for configuring clients, drugs, batches, literature, membership, and API products.
Step 1: Create clients
Go to Sahitya1 > Clients and create a client record. You can assign an existing WordPress user or create a new login so that person can access only their own dashboard data.
Step 2: Add drugs
Go to Sahitya1 > Drugs and attach each drug to a client. This relationship controls what literature appears to that client on the frontend.
Step 3: Create weekly batches
Go to Sahitya1 > Weekly Batches, select the drug, define start and end dates, and set the source database. Weekly batches are the time buckets used for literature grouping and trend charts.
Step 4: Add literature manually or by CSV
Use Sahitya1 > Literature for manual entry, or Sahitya1 > CSV Upload for bulk import. Imported rows become part of your core literature database and can later feed the developer API catalog.
Step 5: Manage products
Go to Sahitya1 > Membership & API to manage the two separate commercial tracks: user membership for tool access and developer API access for external buyers.
Step 6: Review actions
Use Sahitya1 > Audit Log to review saved records, deletions, uploads, and API-related events that the plugin tracks internally.
User
User Guide
Explain how end users log in, activate membership, use filters, and export literature.
How users log in
Users sign in with the WordPress account assigned to their client profile. If the login is not linked to a Sahitya1 client, the dashboard will stay restricted.
How membership works
The membership page is only for dashboard usage. It controls who can log in and use the literature tool. It does not automatically grant API access.
How filters work
Users can filter by date range, title, keyword, year, country, source database, drug, category, and relevance. The dashboard updates totals, trend visuals, and result tables based on those selections.
How exports work
The Export CSV action on the dashboard exports only the visible results for that logged-in client and current filter state.
Developer
Developer API Guide
Describe authentication, endpoints, filters, and the future commercial API model.
API access is separate
Developers use the separate API portal, not the membership page. API keys are tied to developer API access records, not dashboard subscriptions.
Primary endpoint
Use GET https://shudarsana.com/wp-json/sahitya1/v1/catalog with an API key in the x-sahitya1-api-key header or api_key query parameter.
Available filters
The catalog supports title, keyword, year, category, relevance, country, source_database, date_from, date_to, drug_id, limit, and offset.
What the API returns
The API returns literature metadata records from your database without exposing client-identifying information. This allows the literature repository to become a separate sellable product.
Future API sales model
The plugin already stores developer API products, access records, and API keys. Paid checkout, quotas, usage metering, and tiered pricing can be added later without changing user membership.
No documentation items matched your search.
Q&A
Searchable answers
How do I install the main dashboard?
Create a normal WordPress page and place [sahitya1_dashboard] inside it. Assigned client users can then log in and use the literature dashboard.
What page should users visit for membership?
Create a page with [sahitya1_membership]. This page is for end users who want to log in and use the tool.
What page should developers visit for API access?
Create a page with [sahitya1_api_portal]. This page is for developers who want API access, API keys, and future API billing plans.
Does API access include the dashboard?
No. API access and tool membership are intentionally separate products. A developer can have API access without dashboard membership, and a user can have dashboard membership without an API key.
Does uploaded literature become part of the sellable database?
Yes. Literature entries uploaded through admin tools are stored in the plugin database and can be reused later in the developer catalog API, excluding client-identifying details from the public API payload.
How do trend charts group data?
Trend charts group literature by weekly batch date range, not by individual row count. Multiple entries in one weekly batch appear as one weekly point or bar.
Can I use the plugin for free right now?
Yes. The current membership and developer API products can both be activated as free plans. Paid billing is designed for a future phase.
How do I test the API?
Activate API access from the developer API portal, generate an API key, then send a GET request to the catalog endpoint using the key in the x-sahitya1-api-key header.
Guides
4 sectionsPlatform Overview
Understand how Sahitya1 is structured across dashboard usage, admin management, and developer API access.
Sahitya1 stores literature records in a reusable database, lets admins organize that data by client, drug, and weekly batch, and gives assigned users a filtered dashboard to search and export their literature.
The plugin now has three separate layers: the literature database, the user-facing membership for dashboard access, and the developer-facing API product for external integrations.
Use
Client login required
Please log in with your assigned Sahitya1 client account to access literature records and filters.
Sahitya1 Membership
Sign in to access your tool membership, activate the free plan, and manage future subscriptions for the literature dashboard.
Payment, paid subscriptions, and full checkout for dashboard users will be connected after the rest of the platform is complete.
Sahitya1 Developer API
Sign in to activate developer API access, generate keys, and manage your future API plan separately from dashboard membership.
This portal is separate from end-user dashboard membership. Paid API products and request tiers can be attached later without affecting tool subscriptions.
Sahitya1 Documentation Center
Searchable guidance for admins, dashboard users, and developer API buyers.
[sahitya1_dashboard][sahitya1_membership][sahitya1_api_portal][sahitya1_docs]Guides
4 sectionsPlatform Overview
Understand how Sahitya1 is structured across dashboard usage, admin management, and developer API access.
Sahitya1 stores literature records in a reusable database, lets admins organize that data by client, drug, and weekly batch, and gives assigned users a filtered dashboard to search and export their literature.
The plugin now has three separate layers: the literature database, the user-facing membership for dashboard access, and the developer-facing API product for external integrations.
Use [sahitya1_dashboard] for the literature dashboard, [sahitya1_membership] for user membership access, [sahitya1_api_portal] for developer API access, and [sahitya1_docs] for the full documentation page.
Admin Guide
Step-by-step guidance for configuring clients, drugs, batches, literature, membership, and API products.
Go to Sahitya1 > Clients and create a client record. You can assign an existing WordPress user or create a new login so that person can access only their own dashboard data.
Go to Sahitya1 > Drugs and attach each drug to a client. This relationship controls what literature appears to that client on the frontend.
Go to Sahitya1 > Weekly Batches, select the drug, define start and end dates, and set the source database. Weekly batches are the time buckets used for literature grouping and trend charts.
Use Sahitya1 > Literature for manual entry, or Sahitya1 > CSV Upload for bulk import. Imported rows become part of your core literature database and can later feed the developer API catalog.
Go to Sahitya1 > Membership & API to manage the two separate commercial tracks: user membership for tool access and developer API access for external buyers.
Use Sahitya1 > Audit Log to review saved records, deletions, uploads, and API-related events that the plugin tracks internally.
User Guide
Explain how end users log in, activate membership, use filters, and export literature.
Users sign in with the WordPress account assigned to their client profile. If the login is not linked to a Sahitya1 client, the dashboard will stay restricted.
The membership page is only for dashboard usage. It controls who can log in and use the literature tool. It does not automatically grant API access.
Users can filter by date range, title, keyword, year, country, source database, drug, category, and relevance. The dashboard updates totals, trend visuals, and result tables based on those selections.
The Export CSV action on the dashboard exports only the visible results for that logged-in client and current filter state.
Developer API Guide
Describe authentication, endpoints, filters, and the future commercial API model.
Developers use the separate API portal, not the membership page. API keys are tied to developer API access records, not dashboard subscriptions.
Use GET https://shudarsana.com/wp-json/sahitya1/v1/catalog with an API key in the x-sahitya1-api-key header or api_key query parameter.
The catalog supports title, keyword, year, category, relevance, country, source_database, date_from, date_to, drug_id, limit, and offset.
The API returns literature metadata records from your database without exposing client-identifying information. This allows the literature repository to become a separate sellable product.
The plugin already stores developer API products, access records, and API keys. Paid checkout, quotas, usage metering, and tiered pricing can be added later without changing user membership.
Q&A
Searchable answersHow do I install the main dashboard?
Create a normal WordPress page and place [sahitya1_dashboard] inside it. Assigned client users can then log in and use the literature dashboard.
What page should users visit for membership?
Create a page with [sahitya1_membership]. This page is for end users who want to log in and use the tool.
What page should developers visit for API access?
Create a page with [sahitya1_api_portal]. This page is for developers who want API access, API keys, and future API billing plans.
Does API access include the dashboard?
No. API access and tool membership are intentionally separate products. A developer can have API access without dashboard membership, and a user can have dashboard membership without an API key.
Does uploaded literature become part of the sellable database?
Yes. Literature entries uploaded through admin tools are stored in the plugin database and can be reused later in the developer catalog API, excluding client-identifying details from the public API payload.
How do trend charts group data?
Trend charts group literature by weekly batch date range, not by individual row count. Multiple entries in one weekly batch appear as one weekly point or bar.
Can I use the plugin for free right now?
Yes. The current membership and developer API products can both be activated as free plans. Paid billing is designed for a future phase.
How do I test the API?
Activate API access from the developer API portal, generate an API key, then send a GET request to the catalog endpoint using the key in the x-sahitya1-api-key header.
Admin Guide
Step-by-step guidance for configuring clients, drugs, batches, literature, membership, and API products.
Go to Sahitya1 > Clients and create a client record. You can assign an existing WordPress user or create a new login so that person can access only their own dashboard data.
Go to Sahitya1 > Drugs and attach each drug to a client. This relationship controls what literature appears to that client on the frontend.
Go to Sahitya1 > Weekly Batches, select the drug, define start and end dates, and set the source database. Weekly batches are the time buckets used for literature grouping and trend charts.
Use Sahitya1 > Literature for manual entry, or Sahitya1 > CSV Upload for bulk import. Imported rows become part of your core literature database and can later feed the developer API catalog.
Go to Sahitya1 > Membership & API to manage the two separate commercial tracks: user membership for tool access and developer API access for external buyers.
Use Sahitya1 > Audit Log to review saved records, deletions, uploads, and API-related events that the plugin tracks internally.
User Guide
Explain how end users log in, activate membership, use filters, and export literature.
Users sign in with the WordPress account assigned to their client profile. If the login is not linked to a Sahitya1 client, the dashboard will stay restricted.
The membership page is only for dashboard usage. It controls who can log in and use the literature tool. It does not automatically grant API access.
Users can filter by date range, title, keyword, year, country, source database, drug, category, and relevance. The dashboard updates totals, trend visuals, and result tables based on those selections.
The Export CSV action on the dashboard exports only the visible results for that logged-in client and current filter state.
Developer API Guide
Describe authentication, endpoints, filters, and the future commercial API model.
Developers use the separate API portal, not the membership page. API keys are tied to developer API access records, not dashboard subscriptions.
Use GET https://shudarsana.com/wp-json/sahitya1/v1/catalog with an API key in the x-sahitya1-api-key header or api_key query parameter.
The catalog supports title, keyword, year, category, relevance, country, source_database, date_from, date_to, drug_id, limit, and offset.
The API returns literature metadata records from your database without exposing client-identifying information. This allows the literature repository to become a separate sellable product.
The plugin already stores developer API products, access records, and API keys. Paid checkout, quotas, usage metering, and tiered pricing can be added later without changing user membership.
Q&A
Searchable answersHow do I install the main dashboard?
Create a normal WordPress page and place
Client login required
Please log in with your assigned Sahitya1 client account to access literature records and filters.
What page should users visit for membership?
Create a page with
Sahitya1 Membership
Sign in to access your tool membership, activate the free plan, and manage future subscriptions for the literature dashboard.
Payment, paid subscriptions, and full checkout for dashboard users will be connected after the rest of the platform is complete.
What page should developers visit for API access?
Create a page with
Sahitya1 Developer API
Sign in to activate developer API access, generate keys, and manage your future API plan separately from dashboard membership.
This portal is separate from end-user dashboard membership. Paid API products and request tiers can be attached later without affecting tool subscriptions.
Does API access include the dashboard?
No. API access and tool membership are intentionally separate products. A developer can have API access without dashboard membership, and a user can have dashboard membership without an API key.
Does uploaded literature become part of the sellable database?
Yes. Literature entries uploaded through admin tools are stored in the plugin database and can be reused later in the developer catalog API, excluding client-identifying details from the public API payload.
How do trend charts group data?
Trend charts group literature by weekly batch date range, not by individual row count. Multiple entries in one weekly batch appear as one weekly point or bar.
Can I use the plugin for free right now?
Yes. The current membership and developer API products can both be activated as free plans. Paid billing is designed for a future phase.
How do I test the API?
Activate API access from the developer API portal, generate an API key, then send a GET request to the catalog endpoint using the key in the x-sahitya1-api-key header.