Stack Internal
Open Source License and Usage Overview
License Types: MIT License: http://www.opensource.org/licenses/mit-license.php BSD 3 License: https://opensource.org/licenses/BSD-3-Clause New BSD License: http://creativecommons.org/licenses/BSD Apache 2.0: https://www.apache.org/licenses/LICENSE-2.0 Components Animate.css http://daneden.me/animate Licensed under the MIT license Copyright (c) 2013 Daniel Eden Bootstrap v3.3.2 http://getbootstrap.com Copyright 2011-2015 Twitter, Inc. Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE) bootstrap tab collapse plugin the mit license (mit) copyright (c) 2014 flatlogic.com permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "software"), to deal in the software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software, and to permit persons to whom the software is furnished to do so, subject to the following conditions: source: https://github.com/flatlogic/bootstrap-tabcollapse Chess Replayer 1.2.0 Copyright (c) 2012 Andrew Hoy http://github.com/andrewphoy/chess-replayer MIT License CodeMirror copyright (c) by Marijn Haverbeke and others Distributed under an MIT license: http://codemirror.net/LICENSE This is CodeMirror (http://codemirror.net), a code editor implemented in JavaScript on top of the browser's DOM. You can find some technical background for some of the code below at http://marijnhaverbeke.nl/blog/#cm-internals. commonmark.js - CommomMark in JavaScript Copyright (C) 2014 John MacFarlane License: BSD3 Cookie plugin Copyright (c) 2006 Klaus Hartl (stilbuero.de) License: Dual licensed under the MIT and GPL licenses: dat.globe Javascript WebGL Globe Toolkit http://dataarts.github.com/dat.globe Copyright 2011 Data Arts Team, Google Creative Lab Licensed under the Apache License, Version 2.0 (the 'License'); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 D3.v2.js TERMS OF USE - EASING EQUATIONS Open source under the BSD License. Copyright 2001 Robert Penner diff v2.0.1 Software License Agreement (BSD License) Copyright (c) 2009-2015, Kevin Decker <kpdecker@gmail.com> EventEmitter v4.0.1 - git.io/gTW-jg Oliver Caldwell MIT license EventEmitter v3.1.4 https://github.com/Wolfy87/EventEmitter Licensed under the MIT license: Oliver Caldwell (olivercaldwell.co.uk) FancyBox - jQuery Plugin Examples and documentation at: http://fancybox.net Copyright (c) 2008 - 2010 Janis Skarnelis That said, it is hardly a one-person project. Many people have submitted bugs, code, and offered their advice freely. Their support is greatly appreciated. Version: 1.3.4 (11/11/2010) Requires: jQuery v1.3+ Dual licensed under the MIT and GPL licenses: http://www.opensource.org/licenses/mit-license.php http://www.gnu.org/licenses/gpl.html History.js jQuery Adapter author Benjamin Arthur Lupton contact@balupton.com copyright 2010-2011 Benjamin Arthur Lupton contact@balupton.com license New BSD License <http://creativecommons.org/licenses/BSD/> jQuery JavaScript Library v1.7.1 http://jquery.com Distributed in whole under the terms of the MIT Copyright 2010, John Resig Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Includes Sizzle.js http://sizzlejs.com Copyright 2010, The Dojo Foundation Released under the MIT and BSD Licenses. jQuery plugin for getting position of cursor in textarea license under Apache license author Bevis Zhao (i@bevis.me, http://bevis.me) jQuery Color Animations Copyright 2007 John Resig Released under the MIT and GPL licenses. jQuery Autocomplete plugin 1.1pre Copyright (c) 2009 Jörn Zaefferer Dual licensed under the MIT and GPL licenses: http://www.opensource.org/licenses/mit-license.php http://www.gnu.org/licenses/gpl.html Revision: $Id: jquery.autocomplete.js 5785 2008-07-12 10:37:33Z joern.zaefferer jQuery Autocomplete plugin 1.1 Copyright (c) 2009 Jörn Zaefferer Dual licensed under the MIT and GPL licenses: http://www.opensource.org/licenses/mit-license.php http://www.gnu.org/licenses/gpl.html Revision: $Id: jquery.autocomplete.js 15 2009-08-22 10:30:27Z joern.zaefferer jQuery UI Autocomplete 1.8.16 Copyright 2011, AUTHORS.txt (http://jqueryui.com/about) Dual licensed under the MIT or GPL Version 2 licenses. http://jquery.org/license http://docs.jquery.com/UI/Autocomplete#theming jquery.cookie.js Cookie plugin Copyright (c) 2006 Klaus Hartl (stilbuero.de) Dual licensed under the MIT and GPL licenses: http://www.opensource.org/licenses/mit-license.php http://www.gnu.org/licenses/gpl.html jquery.sparkline 1.6 http://omnipotent.net/jquery.sparkline Licensed under the New BSD License - see above site for details Jquery.event.drag.js v1.5 Copyright (c) 2008, Three Dub Media (http://threedubmedia.com) Licensed under the MIT License ~ http://threedubmedia.googlecode.com/files/MIT-LICENSE.txt jQuery.ScrollTo Copyright (c) 2007-2012 Ariel Flesler - aflesler(at)gmail(dot)com | http://flesler.blogspot.com Dual licensed under MIT and GPL. author Ariel Flesler version 1.4.5 BETA jQuery UI CSS Framework 1.8.16 Copyright 2011, AUTHORS.txt (http://jqueryui.com/about) Dual licensed under the MIT or GPL Version 2 licenses. http://jquery.org/license http://docs.jquery.com/UI/Theming/API jQuery UI Menu 1.8.16 Copyright 2010, AUTHORS.txt (http://jqueryui.com/about) Dual licensed under the MIT or GPL Version 2 licenses. http://jquery.org/license http://docs.jquery.com/UI/Menu#theming jQuery UI Datepicker 1.8.16 Copyright 2011, AUTHORS.txt (http://jqueryui.com/about) Dual licensed under the MIT or GPL Version 2 licenses. http://jquery.org/license http://docs.jquery.com/UI/Datepicker#theming jQuery UI Progressbar 1.8.16 Copyright 2011, AUTHORS.txt (http://jqueryui.com/about) Dual licensed under the MIT or GPL Version 2 licenses. http://jquery.org/license http://docs.jquery.com/UI/Progressbar#theming jQuery UI 1.8.16 Copyright 2011, AUTHORS.txt (http://jqueryui.com/about) Dual licensed under the MIT or GPL Version 2 licenses. http://jquery.org/license http://docs.jquery.com/UI jQuery UI Widget 1.8.16 Copyright 2011, AUTHORS.txt (http://jqueryui.com/about) Dual licensed under the MIT or GPL Version 2 licenses. http://jquery.org/license http://docs.jquery.com/UI/Widget jQuery UI Position 1.8.16 Copyright 2011, AUTHORS.txt (http://jqueryui.com/about) Dual licensed under the MIT or GPL Version 2 licenses. http://jquery.org/license http://docs.jquery.com/UI/Position jStat - JavaScript Statistical LibraryCopyright (c) 2011 This document is licensed as free software under the terms of the MIT License: Chosen v1.4.2 | (c) 2011-2015 by Harvest | MIT License, ttps://github.com/harvesthq/chosen/blob/master/LICENSE.md JTab - Javascript/CSS Guitar Chord and Tab Notation for the Web. Version 1.3.1 Written by Paul Gallagher (http://tardate.com), 2009. (original version and maintainer) Contributions: Jason Ong (https://github.com/jasonong) Bruno Bornsztein (https://github.com/bborn) Binary Bit LAN (https://github.com/binarybitlan) See: http://jtab.tardate.com : more information on availability, configuration and use. http://github.com/tardate/jtab/tree/master : source code repository, wiki, documentation * This library also depends on the following two libraries that must be loaded for it to work: jQuery - http://www.jquery.com Raphael - http://raphaeljs.com * This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. * This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. * You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA klass: a classical JS OOP façade https://github.com/ded/klass License MIT (c) Dustin Diaz & Jacob Thornton 2012 Konami-JS Code: http://konami-js.googlecode.com Examples: http://www.snaptortoise.com/konami-js Copyright (c) 2009 George Mandis (georgemandis.com, snaptortoise.com) Version: 1.4.0 (1/21/2013) Licensed under the GNU General Public License v3 http://www.gnu.org/copyleft/gpl.html Tested in: Safari 4+, Google Chrome 4+, Firefox 3+, IE7+, Mobile Safari 2.2.1 and Dolphin Browser Less - Leaner CSS v2.5.3 http://lesscss.org Copyright (c) 2009-2015, Alexis Sellier self@cloudhead.net Licensed under the Apache 2 License. LESS - Leaner CSS v1.7.0 http://lesscss.org Copyright (c) 2009-2014, Alexis Sellier self@cloudhead.net Licensed under the Apache v2 License. MarkdownSharp http://daringfireball.net/projects/markdown * Markdown.NET Copyright (c) 2004-2009 Milan Negovan http://www.aspnetresources.com http://aspnetresources.com/blog/markdown_announced.aspx * MarkdownSharp Copyright (c) 2009-2010 Jeff Atwood http://stackoverflow.com http://www.codinghorror.com/blog http://code.google.com/p/markdownsharp * History: Milan ported the Markdown processor to C#. He granted license to me so I can open source it and let the community contribute to and improve MarkdownSharp. Mathjax-editing.js and mathjax-editing.beta.js https://www.mathjax.org/#docs The MIT License (MIT) Copyright (c) 2016 Stack Exchange Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Modernizr v2.7.1 www.modernizr.com Copyright (c) Faruk Ates, Paul Irish, Alex Sexton Available under the BSD and MIT licenses: www.modernizr.com/license Authors Faruk Ates, Paul Irish, Alex Sexton Contributors Ryan Seddon, Ben Alman Prettify Copyright (C) 2006 Google Inc. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. SamlSchema.cs Copyright (C) 2012 CoverMyMeds Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. This file is taken from https://github.com/covermymeds/saml-http-post-reference/blob/master/CMMSAMLLibrary/SAMLSchema.cs Simple OpenID Plugin http://code.google.com/p/openid-selector This code is licenced under the New BSD License. The Porter2 stemming algorithm author: Kamil Bartocha email: crow2 (at) poczta.fm version: 1.0.0 date: 11.04.2007 This is a C# implementation of the Porter2 algorithm as described on: http://snowball.tartarus.org/algorithms/english/stemmer.html LICENSE: * Copyright 2007 Kamil Bartocha. All rights reserved. * Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * THIS SOFTWARE IS PROVIDED BY KAMIL BARTOCHA ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. TypeWatch 2.0 Original by Denny Ferrassoli / Refactored by Charles Christolini Examples/Docs: www.dennydotnet.com Copyright(c) 2007 Denny Ferrassoli - DennyDotNet.com Coprright(c) 2008 Charles Christolini - BinaryPie.com Dual licensed under the MIT and GPL licenses: http://www.opensource.org/licenses/mit-license.php http://www.gnu.org/licenses/gpl.html Venn.js https://github.com/benfred/venn.js Copyright (C) 2013 Ben Frederickson Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. WOW - v0.1.4 - 2014-02-12 https://wowjs.uk/docs.html Copyright (c) 2014 Matthieu Aussaguel; Licensed MIT
Learn more
Service Level Agreement (SLA) for Managed Cloud Deployment
NOTE: this service level agreement (SLA) for managed cloud applies only to Stack Internal (Business) and cloud-hosted Stack Internal (Enterprise). This agreement does not apply to Stack Internal (Free), Stack Internal (Basic), or Stack Internal (Enterprise on-premises). 1. Overview During the term of any agreement for which Customers have a license for Stack Internal (Enterprise) and Stack Internal (Business), such license includes ongoing coverage and technical support for the software products and services ("Services") provided by Stack Exchange, Inc. ("Stack”). This SLA describes the response that Stack will make to reported issues with the Services, along with a categorization of issue severity. Customers should report all support issues to Stack by opening a ticket on Stack’s support portal. Once a case has been opened, Stack will provide support communication via e-mail or phone to address and resolve the issue, including providing status updates as appropriate, until the issue is resolved. Support cases opened via other means will not be covered by this SLA. 2. Covered systems Stack Internal (Business) Support Services only cover the performance, hosting, and support of the Stack Internal (Business) Service, while Stack Internal (Enterprise) Support Services only cover the performance, hosting and support of the Stack Internal (Enterprise) Service. For clarity, this SLA shall not apply to Stack Internal Free or Basic tiers, early access releases, feature previews (such as Alpha or Beta releases), or non-production sites such as those used for testing. Covered Services do not include any of the associated systems or infrastructures for which the Customer is responsible for operating or managing, which include but are not limited to: VPN endpoint or concentrators, Identity or Authentication Providers, local networks, and ISP connections. Service credits are not available to customers using Services for Proof of Value. 3. Severity levels Severity Level Issue Description Response & Commencement Time Severity 1 - Inoperative The Stack Overflow Internal site is inaccessible or a Core Function is inoperative to a majority of users. Acknowledged and work commenced within 1 hour Severity 2 - Major A Major Function is unavailable to a majority of users or a Core Function is unavailable to a minority of users. Acknowledged within 4 hours and work commenced within 1 business day Severity 3 - Minor A Minor Function is unavailable for a majority of users or a Major Function is unavailable to a minority of users. Acknowledged within 4 business hours and work commenced within 1 business day Severity 4 - Low A Cosmetic Function issue with the site is identified or an issue is identified with a Core, Major, or Minor Function that does not impair its general usage or ability to perform core tasks. Acknowledged within 1 business day Severity 5 - General Inquiry No functionality issue - general questions regarding site usage, functionality, community development, or other questions Acknowledged within 1 business day 4. Service level guarantees Customer's Stack Internal (Enterprise) Services and Stack Internal (Business) Services will maintain a Quarterly Uptime of at least 99.5% In the event that Quarterly Uptime is less than 99.5% but greater than 99%, Customers will receive a pro-rated credit of their license fee, equal to 5% of that quarter's portion of the annual fee. In the event that Quarterly Uptime is less than 99%, Customers will receive a pro-rated credit of their license fee, equal to 10% of that quarter's portion of the annual fee. The Quarterly Uptime guarantee does not apply to Downtime that is due to the direct result of an issue that affects the Microsoft Geographic Region that the service is hosted in unless the Customer has subscribed to a Multi-Region High Availability Disaster Recovery (“HADR”) setup. While Stack takes steps to minimize Downtime, occasionally there will be service interruptions that are beyond Stack’s control and do not constitute Downtime for the purposes of this SLA, including: Slowness or faults with a specific feature (such as search, voting, etc); Delays with uploading or processing files; External network problems outside of Stack’s control, such as bad routing tables between a Customer’s** internet service provider (ISP) and Stack’s servers; "Scheduled Downtime" for maintenance (as detailed below); or Other Acts of God or Force Majeure events. 5. Maintenance windows While most of the work on Services happens silently, occasionally Stack will need to perform maintenance that requires Scheduled Downtime. If Scheduled Downtime for maintenance is necessary, Stack will endeavor to provide Customer’s administrators a minimum of twenty-four (24) hours advance notice via email or notices provided on the Services. 6. Definitions Available/Availability The ability of end-users to reach and display at least one page of the Customer’s Stack Internal (Enterprise) Service or Stack Overflow Service, as applicable. Business Day/Hours Customer Support is available for tickets of all severity between the hours of 12 am Monday and 11:59 pm Friday, eastern standard time, not including US Holidays, office closures. and staff availability. After-hours support is available for Severity 1 and Severity 2 tickets by opening a ticket on Stack’s support portal. Cosmetic Functions User interface issues, all static site content (such as documentation, help pages, or error messages). Core Functions Asking questions, answering questions, searching content, viewing content, and API access. Downtime A time period that the service is not Available. Major Functions Creating/editing users, tags, or other end-user facing organization related functionality. Integrations and 3rd party integrations (Slack, MS Teams, Jira, Github). MCP server access and management for AI/agent workflows. Minor Functions Moderator tools and other site functionality not included in Core or Major functionality. Quarterly Portion The quarterly portion of a license fee shall be defined as equal to 25% of the Annual License Fee as listed on the Order Form or any other applicable ordering document agreed upon by Stack. Quarterly Uptime Quarterly Uptime % = (Maximum Available Minutes-Downtime) / Maximum Available Minutes. “Scheduled Downtime” A time period that the Service is anticipated to be unavailable for more than 5 minutes due to planned maintenance events. Unscheduled Downtime A time period that the Service is unavailable for more than five minutes without planned maintenance events.
Learn more
Stack Internal Enterprise Release Notes
Release 2025.9 (12/17/2025, Stack Internal Enterprise hosted only) Your 2025 Stacked Your 2025 Stacked celebrates the most meaningful contributions to your Stack Internal community and the people who made them. It goes beyond the dashboard to provide a year's worth of interactive insights, spotlighting user engagement and community support. If activity on your site meets these minimum requirements for the previous year, users can access Your 2025 Stacked at https://[your_site].stackenterprise.co/your-2025-stacked. MCP Updates MCP now shows a consent page if a new client initiates the auth flow and the server can't verify an authorization cookie at the /authorize endpoint. This prevents access token theft and provides a more secure MCP experience. MCP now appears as a persistent navigation item under the "Content" section. When MCP is enabled, the /mcp page displays the full configuration and setup view. This includes key highlights, configuration details, prompt and tool references, and integration guides at the bottom of the page. Bug fixes The Learn more link on the Dashboard page now links to the correct URL. We updated the weekly digest on Slack and Microsoft Teams to more accurately report the number of people helped. Fixed indexing errors related to Redis updates. Resolved an issue with ignored tags hiding too much content from the homepage. Removed Close Option from Manage Dropdown for Obsolete Questions. Fixed Collections post count not decreasing when posts in collection are deleted. The Teams header in the left side navigation has been renamed to Private Teams. We've improved enhanced search error handling and performance.
Learn more
Stack Overflow Internal API v3
Overview The Stack Overflow Internal API enables you to interact with your Stack Internal Enterprise site programmatically with external scripts, reporting tools and automated workflows. You can read about general API v3 features in the API v3 Overview article. THIS ARTICLE APPLIES TO STACK INTERNAL ENTERPRISE ONLY. Other Stack Internal users should read this article instead. Find your plan. Access API v3 You'll access API v3 within your Stack Internal Enterprise instance at https://[your_site].stackenterprise.co/api/v3. In addition to this document, your site has interactive documentation with definitions for all API v3 methods and data models. This interactive documentation system (Swagger UI) allows you to test API calls and view returned data in a convenient web interface with no API implementation required. See the "Interactive API v3 documentation" section below for more information. You can access the interactive API documentation at https://[your_site].stackenterprise.co/api/v3. NOTE: To avoid having the API block or throttle your requests, make sure each API request includes a User-Agent header. Learn more in our API v3 Overview article. Authentication and authorization The starting point for API v3 authentication is the API application. An OAuth authentication process uses the API application information to create an API access token. This token then accompanies and authorizes every API v3 request. Access tokens that are read-only can read data only; read-write tokens allow API calls to read, update, and delete data. Only users authenticated into Stack Internal Enterprise can create API Applications and tokens. For more information about the explicit OAuth process, read the Authorization Code Grant (Explicit OAuth) with PKCE article. NOTE: The implicit OAuth process is a legacy method previously used for quickly obtaining access tokens in native apps and JavaScript server-side apps. We do NOT recommend using this method due to security risks. For more information, visit OAuth.net. Manage API v3 applications and service applications API v3 supports two types of API applications: user API applications and service applications. A user API application is owned by the user that created it. Any access token created with that API application ceases to work if the user is deleted or deactivated. A service application is a special type of API application created by a Stack Internal Enterprise administrator and owned by the "Community" user. Unlike user-specific API applications, service applications are persistent and will never be deactivated along with any user account. Only admins can create and access service applications. This table lists the key differences between service applications and regular user API applications. API Application Service Application Created by Any user (including admins) Admins only Owned by Specific user "Community" user Accessible by User who created it Any admin Best for Single-user applications 3rd-party integrations Persistent access Deactivated on user deletion Yes No Site admins can create both service applications and their own API applications, and should consider the following factors when deciding which to use. Access tokens generated by a regular API application are dependent on that API application. If the admin deletes the API application, or if the admin account is deleted or deactivated, the tokens will become invalid. This could interrupt API integrations, potentially compromising site performance or user access. A service application is not tied to (or affected by) the admin's user account, and provides a persistent and stable access point for API integrations. Administrators should use service applications when enabling an integration that's independent of any individual user account. If a third-party integration generates dynamic tokens or requires persistent access to the Stack Internal Enterprise site, for example, a service application is the appropriate choice. Using an API application instead would create an unwanted dependency on a specific user account. If the user is deleted or deactivated, the integration will lose API access and stop functioning. To manage all API applications and service applications from the admin API settings page, click Admin Settings then API under the "INTEGRATION AND APPS" heading. This page shows a table of existing API applications for specific users, as well as service applications (owned by the "Community" user). Click on any column heading to sort the table by that column. To change which applications appear in the list, select All applications, Service applications, or User applications from the upper-right pull-down men. Service applications Only admins can create API v3 service applications. To create a new service application, click Create new service application. The Community user page will appear. Create the new service application with this process: Enter a distinct API application name that helps you distinguish and organize your API applications. Enter the permitted Domain. This should be the domain of the external application you intend to connect with Stack Internal Enterprise, if you don’t intend to connect an external application just use your Stack Internal Enterprise site as a Domain. Click Create API application to create the new API application. Once done, the new service application will appear in the "Active API applications" list for the Community user. API application secrets When you create an API application and provide an optional domain, Stack Internal Enterprise generates a secret as well as a key. You'll use the secret to generate access tokens in some OAuth processes. Stack Internal Enterprise shows the API application's secret only once on initial creation, so be sure to copy it for future use. Later, the secret appears as a string of asterisks for security. You'll see each API application in the Active API applications list. Click Show details to see any application's key and (obscured) secret. If you created an API application but didn't copy its secret, there's no way to access that secret again. Instead, click Rotate secret to generate a new secret you can copy and save. If you generate a new secret, you'll need to use it for all future access tokens for that API application. Access tokens created with earlier secrets will also continue to work. API application permissions All new API applications, including service applications, start with read-only permissions. To change the permissions of a service application, click its select menu in the Status column. When changing a service application's status to Read-write, Stack Internal Enterprise will prompt you for a permitted Domain. Enter (or verify) the domain of the application that will be accessing the API and click Confirm. To change a read-write service application to read-only status, click its Status select menu and select Read-only. Click Disable. To remove a service application entirely, click its trash can (delete) button. User API applications Unlike service applications, user API applications are owned by the user that created them. If the user is removed from the site by deactivation or deletion, their API applications and access tokens will no longer work. An API application's access token has access to the same data as the user that created it. An access token with read-write permissions, for example, can update the same content (questions, answers, comments) as the user. To access the user API application management page, click your avatar (profile picture) at the top of the page. Click Settings, then API applications (under the "APPS & INTEGRATIONS" heading). The API application page has two parts: an upper section to create new API applications, and a table of existing API applications below. To create a new user API application, enter an API application name and your site's Domain. Click Create API application. Your new API application will appear in the "Active API applications" table. To change the permissions of an API application, click the select menu in that API application's "Status" column. When you enable write access, you'll be prompted to enter or confirm the domain of the application that will be accessing the API. To delete an API application, click its trash can (delete) button. The API will then reject any future calls that use the deleted API application's access token(s). The admin settings API application page is similar to the user API applications page, but with additional controls. The admin page allows control of service applications as well as all user API applications. Admins can delete user API applications, change their read-only/read-write scope, and update domains. Write API access If you authorise an API access token with write access, you can use it to perform write operations. This includes submitting and editing questions and answers, as well as voting and editing. The site credits these actions to the user that authorised the access token, so don't share your write-enabled access token with other users. Interactive API v3 documentation Admins can enable or disable the interactive API v3 documentation (Swagger UI) by scrolling to the bottom of the API applications page and clicking On or Off. When on, Stack Internal Enterprise creates a dedicated service application for Swagger UI. If you disable Swagger UI, Stack Internal Enterprise will delete the Swagger UI service application. To access the interactive documentation, click Go to Swagger UI (or navigate to https://[your_site].stackenterprise.co/api/v3). To download a JSON file of all API v3 endpoints and models, click Download. Swagger UI access tokens The Swagger UI interface functions as a service application with full access to API v3 as the authenticated user. When authorized, Swagger UI uses its service application to create an access token. This token expires after 24 hours. NOTE: You don't have to wait for the 24-hour period to end to create a new Swagger UI access token. To delete the existing token and create a new one, click Authorize, then Logout, then Authorize again. To authorize Swagger UI and create a new access token: Go to https://[your_site].stackenterprise.co/api/v3. Click Authorize. An OAuth explicit flow (with PKCE) prompt will appear. Leave client_id unchanged. Leave client_secret blank. Check write_access if the token should have write permissions. Check access_team if the token is for a private team and not the main site. Choose the private team and click Continue. Click Approve. When you use Swagger UI to access API v3, Swagger UI reveals the access token as part of the underlying API call. You can find the access token in the "Curl" section of the Swagger UI execution output. Look for the following line: -H 'Authorization: Bearer [access_token]' You are free to use this token outside of the Swagger UI, but only temporarily. The token will expire and become unusable 24 hours after creation. API rate limits As of October 1, 2025, existing customers can make 10,000 API calls per day per application or 50,000 API calls per day across all applications. Customers signing up after October 1, 2025 can make 500 API calls per day per application or 1,000 API calls per day across all applications. You can increase these limits with a Premium API plan. Learn more in the Stack Internal Premium API article.
Learn more
Your Year Stacked
Overview Stack Internal Enterprise includes a Your [year] Stacked page to celebrate your users' contributions and community impact over the previous calendar year. This Stacked retrospective page goes beyond the dashboard to highlight a year's worth of achievements in a visually engaging way. Your users can access the Your [year] Stacked page at https://[your_site].stackenterprise.co/your-[year]-stacked. For example: https://[your_site].stackenterprise.co/your-2025-stacked. The page has two main sections, one recognizing individual contributors and the other spotlighting the most popular content. Top contributors The retrospective page includes a "Top contributors" section. Top contributors categories include: Most helpful The users who received the most upvotes, reactions, bookmarks, and follows on their posts (questions, answers, and Articles) from unique users during the year. Most knowledgeable The users who wrote the most answers and Articles during the year. Most supportive The users who gave the most upvotes and created the highest number of reactions, bookmarks, and follows during the year. Most connected The users who wrote answers across the highest number of distinct tags during the year. Most dependable The users who logged in the highest number of times during the year. Most curious The users who asked the highest number of questions during the year. Most attentive The users who reviewed the highest number of questions and Articles in the Content Health Review queue. Popular contributions The retrospective page also includes a content-focused "Popular contributions" section. Popular contributions categories include: Answer of the year The active answer with the highest number of total votes (upvotes and downvotes), follows, and views during the year. Most popular tags The most-used tags across all questions, answers, and Articles during the year. Most popular user groups The most popular user groups based on the number of times they were mentioned in questions and comments during the year. Most popular questions The most popular questions based on the number of views, votes, bookmarks, and follows during the year. Minimum requirements Your Stack Internal Enterprise site will have a Your [year] Stacked page only if it meets all of the following criteria for the previous year: At least 90 days old At least 25 questions At least five articles At least five answers At least six activated users At least 10 upvotes, reactions, bookmarks, and follows by at least three unique users
Learn more